Drive the control plane with a scoped key.
Agents and app backends can call the same surface: generate contracts, inspect provider context, run compliance checks, and simulate supported operations before live provider rollout.
Scoped bearer keys
Keys can be limited by resource, such as compliance, payments, wallets, projects, analytics, or FX.
Compliance before execution
Screening and policy evaluation run before the normal provider execution path continues.
Contract lifecycle
Generate, compile, validate, simulate, deploy, verify, and launch through the agent contract endpoints.
Start with simulation. Move to live providers only when the corridor is ready.
The developer story is not a magic 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 -> deployThe practical developer path is short.
You do not need a generic docs maze on the public site. Start with a key request, a readiness boundary, and the endpoint family you intend to use.
Name 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.