?whatcanido
Open Studio
04 / payments

Take payment for every action that should cost something.

Some actions cost you money to run, or earn you money when an agent calls them. We built two ways to take payment that work right out of the box. Tiny per-call fees in stablecoin (think a fraction of a cent), or real bookings through Stripe (a $50 haircut, a $200 vet visit). The agent always pays before the work happens, so nothing is free unless you want it to be.

01two ways to take money
for tiny per-call fees

Crypto micropayments

  • Cents (or fractions of a cent) per call, costs that don't fit on a credit card
  • Stablecoin on Base, the cheapest network for this
  • No account, no checkout, just a signed approval the site verifies on chain
  • Right for: API tipping, paid lookups, AI-on-AI workflows
Read the spec
for real bookings & orders

Stripe Checkout

  • Standard credit-card checkout your customers already trust
  • Money goes straight to your bank account, we never touch it
  • Refundable, taxed, statement-friendly
  • Right for: $10–$1,000+ haircuts, vet visits, deliveries, deposits
Wire it in Studio
02how a paid call works

Five steps from asking to paid & done.

  1. 01
    Agent tries to do something that costs money.
    It calls the action like any other, no payment attached, just the request.
    POST
  2. 02
    Site sends back the price tag.
    How much, who to pay, on which payment network. The agent now knows exactly what's required.
    402
  3. 03
    Agent signs the payment.
    It produces a tiny cryptographic approval, like signing a check, but instant and free to create.
    viem
  4. 04
    Agent retries, this time carrying the payment.
    Same request, with the signed approval attached.
    POST
  5. 05
    Site verifies the payment, then runs the action.
    The signature gets checked, the money moves, your code does the work, and the audit log records who paid.
    200
what your site sends back when payment's required402
HTTP/1.1 402 Payment Required
Content-Type: application/json
X-Payment-Required: x402

{
  "x402_version": "0.1",
  "challenges": [{
    "scheme":   "exact",
    "network":  "base",
    "asset":    "0x833589fCD6e...02913",
    "max_amount_required": "5000",
    "pay_to":   "0xMerchant...",
    "resource": "/api/b/tadeas-reads/premium_search"
  }]
}
03why crypto, for tiny fees

Credit cards weren't built for one-cent transactions. The processing fee alone is more than the payment. They also assume a human is sitting at the checkout, tapping Apple Pay, entering a CVC, getting a 3-D Secure SMS. None of that works for an agent.

So for small per-call fees, we use a crypto standard called x402. The agent signs a tiny payment approval, your site verifies the signature, and the money moves. No accounts, no checkout pages, no human-in-the-loop required. The user can still supervise (“you're about to spend $0.10, ok?”), or set a budget and let the agent pay automatically up to that limit.

04and stripe, for real bookings

The crypto rail is great for cents-to-a-few-dollars actions , paid lookups, premium API calls, tipping. Above $5 it stops making sense. Customers want refunds, disputes, statements, familiar checkout pages. That's where Stripe comes in:

  • Money goes straight to your bank account. We never touch it.
  • Standard credit-card checkout your customers already trust , Apple Pay, Google Pay, the works.
  • Refundable, taxed, statement-friendly. Use it for haircuts, vet visits, deliveries, deposits. Basically anything that feels like a normal purchase.
ship a paid action

Add a paid door.

Tell Studio in chat: “make search_recipes paid at $0.05”. We wire the 402, stamp the wallet on the action, and you are collecting at the slot.

Open Studio