Developer surface
One product contract. Built for agents first.
Proofstate executes verified internet actions as infrastructure. Every transport — MCP, REST, SDK, CLI — is a projection of the same typed contract: the same authorization, the same tenant isolation, and receipts that prove what actually happened.
MCP · CODE MODE
Two tools expose the whole control plane.
Instead of dumping dozens of narrow tools into an agent's context, Proofstate advertises exactly two MCP tools. The agent discovers the registry through proofstate.code.search and composes any operation through proofstate.code.execute — measured at a ~94% smaller tool surface than a per-operation projection, with full registry discovery still fitting in a few thousand tokens (chars/4 proxy).
proofstate.code.searchrequires capabilities:read
The canonical operation registry as data: every operation with its JSON Schema, required scopes, side-effect class and idempotency policy. Query or dump it — the agent discovers the whole control plane at runtime instead of hard-coding tool lists.
proofstate.code.executerequires code:execute
Runs bounded JavaScript in an isolated sandbox whose only bridge is proofstate.request() — compose, chain and fan out registry operations with Promise.all. The sandbox holds no host authority; every bridged call re-checks the token's native scopes, tenant and policy exactly as REST would.
Composition is not escalation. Every bridged call re-enters the same gateway the REST surface uses — the same scope checks, the same tenant and workspace isolation, the same idempotency ledger, the same receipts. Batching evidence is the only thing code-mode composition adds. Long-running work continues server-side as missions that outlive the sandbox; re-attach with missions.get / missions.receipt through code.execute to collect the durable receipt.
Transports
REST v1 + OpenAPI
Gateway REST v1 at https://api.proofstate.dev — status, capabilities, workspaces, missions, workflows, operations, identities, runtimes, memory, tokens, receipts. The OpenAPI 3.1 document at /v1/openapi.json is GENERATED from the canonical operation registry — never hand-written. Bearer-token authorization, bounded scopes, workspace and tenant restrictions on every call; Idempotency-Key honored with exact replay semantics.
MCP — CODE MODE
Streamable HTTP at https://api.proofstate.dev/mcp. The agent surface is deliberately TWO tools: proofstate.code.search and proofstate.code.execute. Read-only resources (proofstate://workspace|mission|workflow/receipt) are available as MCP resources. Legacy browseros.* names are accepted transiently when explicitly called and never advertised.
SDK
TypeScript SDK in this repository — generated from the same contract module the server enforces; drift between SDK and contract is a test failure. In-repository during early access and not published to npm.
CLI
`proofstate` on the command line — status, capabilities, workspaces and reliability operations, plus `proofstate verify` for offline Ed25519 attestation verification against a published public key. The legacy `browseros` invocation remains an alias during the domain transition and runs the identical implementation.
Guarantees
Verified outcomes
Executions end in receipts with verification records — an outcome is successful when the evidence holds, not because the agent said so. Outcomes that cannot be proven are reported as unverified or unknown, never rounded up to success.
Composition, not escalation
code.execute grants the ability to compose operations, not new authority. Every bridged call re-checks native scopes: a token without a grant sees that tool absent from tools/list, and revoking a token takes effect on the next bridged call mid-composition.
Absent, not refused
A tool or operation a token may not call is ABSENT from its tool listing — one consistent law across MCP, REST, SDK and CLI.
Human approvals
Where a human must decide, execution stops at a safe boundary — operator-gated, never bypassed by any transport.
One contract, every transport
REST, MCP, SDK and CLI are projections of one canonical operation table: same authorization, same tenant isolation, same idempotency ledger, same receipt shape. Contract drift is a test failure.
Contract facts
Contract version
2.3.0 — the version the server publishes in /v1/status and stamps into every generated OpenAPI document. This page imports it from the domain contract; it cannot drift from the registry.
MCP surface law
tools/list advertises ONLY what the token's scopes allow: exactly two tools (proofstate.code.search, proofstate.code.execute) — and only code.search without the code:execute grant. An unauthorized tool is ABSENT, not listed-and-refused.
Compatibility law
Legacy browseros.* tool names and browseros:// resource URIs are accepted transiently when explicitly called, but are never advertised. New integrations use proofstate.*.
Idempotency
The same idempotency ledger serves every transport: a replayed key returns the same result over REST, MCP or the SDK — and a digest mismatch is an idempotency_conflict, not a duplicate side effect.
No invented claims
Capability state is read live from GET /v1/status. This page states contract facts only — no fabricated metrics.
Questions about the integration surface? Start from the live API status — it reports the product identity, contract version, and capability snapshot in real time.