Make a first governed call
Public documentation preview — incomplete. This synthetic example is not proof of the full installed-consumer matrix, release readiness or live-provider compatibility. The package remains private and unpublished.After installing a verified candidate, save this as
first-call.mjs in your fresh ESM consumer. It uses only the core package and a synthetic in-process handler. No model, MCP server, credential, or external network request is required.
node first-call.mjs after installation. This exact snippet was exercised locally against a previously installed development candidate: its synthetic result reported status: 'executed' and sideEffectState: 'completed'. That focused check does not establish a freshly packed candidate, an offline-isolated runtime matrix or a live-provider result. Removing policy means default-deny with zero handler dispatch, but that negative case is not tested by this site’s focused snippet check. The demo-host identity is a local fixture: production callers must authenticate identity and authorize the actual resource, tenant and arguments. Keep close() in finally and check the returned status rather than assuming every call succeeds.
Next: choose a connected integration path.