Getting Started

Hosted preview

A managed arbiter endpoint. Same binary, same writ DSL, same SSE protocol — we run the server, you authenticate with a bearer token. Useful when you want to call arbiter from a web app or automation without operating infrastructure yourself.

Status: limited preview. Access is invite-only while we tune capacity and pricing. Joining the waitlist costs nothing; invites go out in waves.

What you get

  • A bearer token tied to a workspace, scoped to your tenant.
  • The full HTTP+SSE API documented in api/: POST/v1/orchestrate, agent CRUD, conversations, structured memory, artifacts, A2A.
  • Sandboxed execution. /exec is disabled in the hosted environment; /write streams files back to your client rather than landing on a server disk. See cli/api.md.
  • Usage telemetry and quota enforcement via the runtime's billing protocol — the same shape as the self-hosted ARBITER_BILLING_URL integration, just preconfigured.

What you don't get (vs. local)

  • /exec — no shell on the server side. If you want agents that run shell commands, use local install.
  • A persistent local working directory — agent file output streams as file SSE events to your client.
  • Direct filesystem access. All persistent state lives behind the API: artifacts, structured memory, scratchpads.

Once provisioned

You'll receive a bearer token and an endpoint URL. Smoke-test it:

curl -N -H "Authorization: Bearer atr_..." \
     -H "Content-Type: application/json" \
     -d '{"agent":"index","message":"hello"}' \
     https://<your-endpoint>/v1/orchestrate

The response is a Server-Sent Events stream. Event shapes are documented in concepts/sse-events.md; the full request/response contract for the orchestrate call is at api/orchestrate.md.

From there, the rest of the API works the same as a local --api server — the hosted endpoint is just a --api server somewhere else.

Next steps