Products Solutions White-label Developers Pricing Blog Sign in Get started
Build on top · 11

Agent payments.

Native HTTP 402 and the x402 protocol. AI agents pay your API, your services, and your merchants directly — no human in the loop.

01

x402 native

Respond 402 with a price; the agent pays in USDC and retries. We handle settlement per call.

02

Per-agent controls

Spend limits, rate limits, and allowlists per agent identity. Kill switch included.

03

Auto-refill wallets

Agent spending wallets refill from treasury on thresholds, so the loop never stalls.

At a glance

The numbers that matter.

Integration

Five lines, like everything else.

x402 middleware 200 OK

Request

app.get("/v1/research", x402({
  price:  "0.42",
  token:  "USDC",
  payee:  "mizu.studio"
}), handler);
Live

Watch an agent pay its own way.

A 402 response names the price. The agent pays in USDC, retries, and gets the resource — settlement happens per call, with no card on file and no invoice at month-end.

agent: research-bot-7 · wallet 0x7a…f2e1 · spend limit $50/day
$ GET api.mizu.studio/v1/research?q=fx-corridors ← 402 Payment Required · price: $0.42 USDC · payee: mizu.studio $ x402 pay 0.42 USDC → mizu.studio confirmed · Base · 1.2s $ GET api.mizu.studio/v1/research?q=fx-corridors ← 200 OK · 184ms · wallet balance $41.18 · auto-refill at $25 from treasury · today: 114 calls · $47.88 settled · 0 disputes

Ready when you are.

Open to every business. Create an account in minutes, build in the sandbox, and go live once your business is verified.

Get started Launch the sandbox