Developers

The routes that exist.

Owner routes, provider routes, a roadmap.

In this preview

GET /api/health

Public. Reports an engineering preview. It describes the service state without claiming a commercial connection.

Workspace, mandates, records

Signed-in owner, bearer token. Create a workspace, save an immutable mandate, revoke it, and read that organization’s audit events, pending approvals, invites, and receipts.

POST /api/tools/propose

Signed-in owner. The studio’s policy lab. A purchase or contract is refused. An over-cap proposal becomes an approval. The check stays inside the product.

POST /api/approvals/:id/decide

Signed-in owner. Accept or reject one exact proposal. Accept means sandbox discussion.

Consent link and /api/consent

The owner creates a one-time link. The other party accepts, declines, or withdraws with the invited email and four acknowledgements. The raw token is not stored.

Participant session routes

After consent, the browser can ask for a capped session, read status, and end it. The session capability is the authority. The page does not send the owner’s money cap.

Provider tool routes and webhooks

Called by the voice provider with its own authentication. They check a proposal, read an owner decision, and can accept a signed post-call callback. The callback is not registered, so it has not produced a live receipt.

Transcript export and deletion

The owner can download the app transcript JSON or delete that app copy. Provider deletion is separate.

Planned

  • A public API credential and a published SDK.
  • Self-serve webhook registration.
  • Telephony, meeting join, and agent-to-agent sessions.
  • Billing, metering for customers, and a partner marketplace.
  • A multilingual session API.

Try it in the studio. Boundaries are on Trust. Module status is on Modules. Contact is not an API signup.