Skip to main content
Stable treats AI agents as first-class accounts. An agent holds a self-custodied wallet, looks up docs and chain state through MCP servers, and pays for services per request through x402 — no card on file, no API key rotation, no human in the loop for routine spend. This tab covers how to equip an agent to build on Stable and how to monetise APIs for agent consumption.

​
What you can build

  • AI-assisted development against Stable’s Docs MCP and Runtime MCP servers inside Cursor, Claude Code, or any MCP-compatible client.
  • Agent skills that combine docs lookup, simulation, and on-chain execution into one workflow (for example, “send 100 USDT0 to three addresses”).
  • Paid MCP tools: wrap x402 APIs as MCP tools so an AI client calls them through prompts and pays per call.
  • Agent-payable APIs: price an HTTP endpoint per request in USDT0 so any agent with a wallet can consume it without a sign-up.
  • Agent wallets funded with USDT0 only, no custodial middleware.

​
How Stable differs

  • Single-asset agent wallets. USDT0 is the gas token and the payment token, so an agent doesn’t juggle ETH + USDT separately.
  • Sub-second settlement. A paid API call settles inside the HTTP lifecycle (~700 ms block time).
  • x402 on ERC-3009. The facilitator submits the on-chain call; the agent only needs to sign an authorization.

​
Start here

Develop with AI

Wire Docs MCP and Runtime MCP into your AI editor and paste the Stable context block.

Pay with an MCP server

Expose x402-paid APIs as MCP tools an agent can call through natural-language prompts.

AI/Agents guide index

Full list of agent guides, facilitator references, and agent wallet specs.

Agentic facilitators

Settlement services for agent-to-agent commerce on Stable.

Build a pay-per-call API

The x402 server that MCP tools wrap.
Last modified on April 23, 2026