Skip to content
Request a Briefing

Drive the control plane with a scoped key.

Developers

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.

Request a Briefing →Explore the sandbox
{}Scoped key request
Sandbox
Surfaceagent API
Resourcescontracts, compliance, directory
Environmentsandbox or production
Boundarysimulation until live providers are connected
✓Least-privilege key
resource-scoped + environment-aware

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.

One gateway. Two ways to connect.

Agent gateway

The 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.

CLI MCP

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.

$ npm install -g @stablecoin/cli

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.

$ npm install -g @stablecoin/agent-gateway

MCP

Run the stdio gateway from an MCP-compatible host such as Claude Code or Codex. The host discovers the same narrow capability set and sends calls with a scoped bearer key.

Request access →Install the MCP gateway ↗View the CLI package ↗

Request access 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.

Quickstart

The developer story is not a magic live-money API. It is a scoped control plane with explicit readiness boundaries.

request
POST /api/v2/agent/contracts/generate
Authorization: Bearer scoped_key

{
  "template": "payout-token",
  "asset": "USDC",
  "network": "base-sepolia"
}

next: compile -> validate -> simulate -> deploy

The practical developer path is short.

Path

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.

Public docs boundary: detailed endpoint references are kept behind access for now. This page should explain the developer surface without exposing private app routes or implying live provider execution.
Request access ->