Paid APIs your agent can settle on Sui

Sui Agent Payments is the payment layer for agents and APIs on Sui. An unpaid request gets one HTTP 402. The owner funds a spend account and authorizes an agent with a scoped grant. The agent holds its own delegate key and settles on chain. There is no buyer signup.

This build is Sui testnet.

Why Sui Agent Payments

No account for buyers

Authority is an on-chain spend account plus a scoped grant, not a Sui Agent Payments user.

The owner stays the owner

The owner funds the account and signs grant create, pause, and revoke. The agent never holds the owner wallet.

The agent holds its own key

MCP OAuth and the SDK both use an agent-held delegate key. The platform never provisions or stores that secret.

One 402, one settlement

MPP and x402 can share one economic offer. Exactly one settlement may succeed per challenge.

What's included

• Console at suipay.dev — fund a spend account, authorize agents, register a paid service.
• Agent skill at /SKILL.md — machine instructions for discovery, pay, and receipt checks.
• Remote MCP — hosted agents connect, complete OAuth, then pay.
• Buyer SDK — createPayer from @cmdoss/suipay-buyer.
• Seller template — copy a Docker seller, set SUIPAY_GATEWAY_ISSUER and SUIPAY_GATEWAY_JWKS_URL. No seller SDK to install.
• MCP — local stdio @cmdoss/suipay-mcp and hosted /mcp (prepare-only).

Choose your path

These paths share one spend account. Pick the door that matches how you run.

Explore the docs

Get started — numbered first call for agents and sellers.

Integrate — MCP, SDK, REST, and how an owner authorizes a key.

Concepts — spend account, grants, rails vs dialects, receipts.

Reference — HTTP 402, service discovery, delegated-signer API.

A machine-readable index of this site is at /llms.txt on the docs host. Agents that need to pay should still start from the console skill, not this host.