Docs
Documentation.
Settle is a stablecoin payment rail. The customer pays an invoice in USDC on Base; the router contract atomically splits the payment 99.5% to the merchant, 0.5% to Settle, in a single on-chain transaction. Non-custodial. No chargebacks.
Start here.
If you have an AI agent in your editor — Cursor, Claude Code, Windsurf — the fastest path is to point it at our MCP server. The agent reads your framework, picks the matching integration pattern, and ships a working checkout in under five minutes. Most merchants finish onboarding in one prompt.
Quickstart is the human version of the same path. It takes about five minutes if you copy the code.
The surface.
There are two ways to drive Settle programmatically and they expose the same primitives.
- MCP — hosted at
mcp.settle.xxx. OAuth-style auth, streamable HTTP. Your agent gets a scoped token and the full tool surface. - REST API — hosted at
api.settle.xxx. Bearer-token auth withsk_live_…orsk_test_…. Same primitives, just over HTTP.
Concepts.
Three short pages cover the things you must understand before integrating.
- Settlement — what “settle” means, why payments are atomic, why there’s no refund mechanism.
- Non-custodial — how payout addresses are registered and verified, and where funds actually live.
- Fees — the 0.5%, gas, the USDT-on-Ethereum threshold rule.
Integration patterns.
Paste-and-go server route + webhook handler for the four frameworks we cover natively. The MCP get_integration_pattern tool returns the same code, so your agent and these pages stay in sync.