Give agents context they can use and boundaries they cannot cross.
DevelopersScoped keys limit what an agent can request. Rules evaluate the operation. Approval state controls what can proceed. Evidence stays with the decision.
Ask these before you issue a key.
The control questionsWhat can this key request?
Bearer keys are limited by resource — contracts, compliance, payments, wallets, projects, analytics, or FX. A compliance key cannot move funds.
What will the rules evaluate?
The same gate the UI uses evaluates the operation before a supported provider path continues. An agent can explain the decision. It cannot override it.
What stays blocked until the corridor is ready?
Mint, burn, and corridor payments simulate today. Live sanctions screening, KYC, and reserve attestation wait until the required providers and evidence are in place.
One gateway. Two ways to connect.
Agent gatewayThe external gateway keeps discovery and read-only operations consistent across tools. Both paths use the same capability names, input rules, and scoped bearer-key boundary.
One gateway boundary
The Agent API owns the allowlisted read-only status view. The same gateway contract serves a scriptable CLI or an MCP host, with authentication scoped to the resources and environment your workflow needs.
CLI
Use scriptable commands to list capabilities, inspect their contracts, and invoke supported read-only operations. JSON output is available for shell scripts and agent runs.
MCP
Connect Claude Code or Codex with existing-account OAuth sign-in, or use an API key for unattended scripts. Discover stack planning, regulatory research, provider capabilities, and permitted organization reads.
Request a walkthrough opens the early-access form. The npm links open the public package pages.
Start with simulation. Move to live providers only when the corridor is ready.
QuickstartThe developer story is not a live-money API. It is a scoped control plane with explicit readiness boundaries.
POST /api/v2/agent/contracts/generate
Authorization: Bearer scoped_key
{
"template": "payout-token",
"asset": "USDC",
"network": "base-sepolia"
}
next: compile -> validate -> simulate -> deployName the flow. Request the scope. Simulate first.
PathName the flow.
Payouts, escrow, issuer operations, or agent-operated treasury. The flow determines provider categories and scopes.
Request the scope.
Ask for only the resources the workflow needs. A compliance-only key should not reach payments.
Simulate before live rollout.
Use builtin adapters and test chains to validate behavior before live provider credentials are connected.
