Give your agent a way to check out.

Your agent can find anything. It can't pay for anything. One API call mints a checkout link — the agent hands it to its operator, the human clicks pay. The money goes straight to you.

# your agent finds the thing, then:
curl -X POST https://agent-checkout.mrdavesemailaddress.workers.dev/v1/checkout-links \
  -H "Authorization: Bearer YOUR_KEY" \
  -d '{"amount_cents": 900, "product_name": "Widget"}'

# → {"payment_url": "https://checkout.stripe.com/..."}
# hand the URL to your operator. done.

How it works

1

Your agent gets a key

One POST, no card, 30 seconds. Then link your Stripe account — about 3 minutes with Connect, or paste your own Stripe key.

2

Your agent makes a link

POST the product and price. Get back a checkout URL on your Stripe account.

3

Your operator pays — you get paid

They check out with Stripe. Funds settle directly to you. We never hold your money.

Three ways to sell. Connect (recommended) — link your Stripe account, we take a small app fee on paid plans, $0 on free. Bring your own key — use your own Stripe key, zero fees from us, stored encrypted. How the modes work →

Try it

Demo mode — no real link is created, nothing is charged. This shows exactly what your agent gets back.

Pricing

Free forever tier. Paid plans are cheap on purpose — launch pricing, locked while we're in beta.

Free
$0/mo
  • 100 links / day
  • All API endpoints
  • MCP server
Get a key
Starter
$9/mo
  • 1,000 links / day
  • Link analytics
  • Email support
Subscribe
Pro
$29/mo
  • 10,000 links / day
  • Everything in Starter
  • Priority support
Subscribe

Full comparison →

Built for agents, readable by agents

Every endpoint is documented in llms.txt — your agent can read the whole API in one fetch. There's also a dependency-free MCP server it can run locally.

The human always pays. Agents generate links; they never complete payments. Stripe handles checkout directly with your operator.