Afraid to give an AI agent your card? Good. Don't.
Every payment your agent tries is decided first: allowed inside your limits, held for your approval above them, or refused. Every decision leaves a signed receipt you can check without us.
Sandbox first — no card, no real money. Real purchases only when you decide.
You start in a sandbox with test money. Nothing real moves until you verify your identity and connect a real account of your own.
Connect your agent
Pick the way your agent lives. An agent in the sandbox connects in about a minute; your own Stripe account takes about ten, six of them yours. Each dark box is meant to be copied as is.
Your own Stripe connects after you go live: an identity check and a passkey, about five minutes. From then on every refund, charge, credit, coupon and payment link your agent attempts is decided against your limits first, and the Stripe key stays in Regent's vault. The agent never holds it.
- Sign up and confirm your email.
- Verify your identity (a document and a selfie, about three minutes), then press Go live on the same screen. It is one-way.
- Add a passkey in Settings: budgets and approvals are signed with it.
- In Stripe: Developers → API keys → Create restricted key. Write: Payment Intents, Charges, Refunds, Transfers, Invoices, Webhook Endpoints. Read: Account information. Add Payment Links, Coupons or Credit notes only if your agent uses them: the key stays the outer wall.
- In the console: Connect → Gateway → paste the
rk_…key. Regent registers the webhooks itself. - Connect the agent with one of the boxes below, or point a Stripe agent at Regent instead of
mcp.stripe.com:
claude mcp add --transport http stripe https://gw.regentprotocol.org/gw/mcp/stripe
Tested by us in Stripe test mode: payment, payment link, refund, transfer to a seller and invoice, each closed by Stripe's own webhook. Before you go live the same tools run on Regent's Stripe test account. Platforms that pay sellers: see the Stripe page for the extra permissions. Stripe App: soon in the Stripe Marketplace.
Any assistant that can open a link
Easiest start: Instinct or Tab — install, paste this prompt.
Paste this to your assistant. It reads our page for agents, creates itself in Regent and walks you through the rest.
Connect to Regent by https://docs.regentprotocol.org/agent and guide me.
Use the Regent sandbox. Make one purchase that is allowed, one that is refused and one that asks me first. Show me the receipt for each.
Tested by us with Instinct, Tab, Hark, Eden and Wabi. Muse, ChatGPT and Grok we have not tried ourselves yet: an assistant that cannot send web requests itself will ask you to add Regent as a connector instead, the same three steps as for Claude. Tell us how it went. Never send your assistant a screenshot of the console or any key.
Claude, on the web or desktop
- Claude.ai
- Claude Desktop
- Settings → Connectors → Add custom connector.
- Paste the address below. Leave client ID and secret empty.
- Connect, sign in to Regent, approve the screen that sets your limits.
https://gw.regentprotocol.org/gw/mcp
Tested by us.
Claude Code
Add Regent, then run /mcp inside Claude Code to sign in.
claude mcp add --transport http regent https://gw.regentprotocol.org/gw/mcp
Tested by us.
Terminal agents and your own code
- Hermes
- Codex
- Python
The first command prints a link: open it, approve with your passkey, and the agent gets its own key. The hook checks every money call before it runs.
pip install regent-control
regent-control onboard --name "My agent" --vendor "Hermes" --purpose "office supplies"
regent-control hook install hermes # or claude-code, codexThe Claude Code hook is tested by us. The Hermes and Codex hooks are new: tell us how they behave.
Names are used to describe compatibility; no partnership or endorsement is implied.
What you can use it for
Each line says how ready it is today, so you know what you are testing.
For you
- Shop with your own card, under a ceiling
Amazon, Walmart, Target and Best Buy through Agentcard. Your card number stays with Agentcard; your agent never sees it.
Early · US card - Approve the big ones from your phone
Anything above your allowance waits for a tap and your passkey. The agent then repeats the same request and it goes through.
Live - Stop your agent in one tap
Revoke it, and its next payment is refused. We measured under half a second.
Live - Receipts you can check yourself
Amount, store, who approved and how, signed. Verify with our open-source tool, without asking us.
Live
For your business
- A support agent that refunds within limits
Per day, per month and per customer, for example no more than $100 refunded to one customer a month.
Live · Stripe - Billing and retention agents
Payment links, coupons, credits and invoice changes are decided like money, against the same budget.
Live · Stripe - One agent, one set of limits
Each connected app is its own agent with its own budget, history and kill switch. Nobody shares a key.
Live - Evidence for disputes and reviews
Export one file per decision. Anyone can verify it offline; change one byte and it fails.
Live - Cards your agent holds
Every authorization on a Stripe Issuing card decided in real time, before the card network answers. Available when Stripe enables Issuing on your account; tell us if you want to be first.
Soon · Stripe Issuing
For builders
- Pay-per-request APIs in USDC
When an API answers 402, the gateway pays it from your wallet under your budget (x402).
Test network · Base Sepolia - Two-signer wallets
A wallet where Regent co-signs only what the gate allowed (Privy). The agent alone cannot move funds.
Test network - Hooks for coding agents
Every tool call that moves money is checked first; the agent's code does not change.
Live · Claude Code Early · Codex, Hermes - Python SDK
Livepip install regent-control. One decorator guards a function that spends.
Seven things to try in the sandbox
Ask your agent to do each one. Each line shows what you should see and the answer code your agent gets.
- Buy something smallGoes through, with a receipt.allow · rcp_…
- Buy something over your per-purchase limitRefused before the shop or Stripe sees it.deny · MANDATE_LIMIT_EXCEEDED
- Buy something above your allowanceWaits for you. Approve it, and the agent repeats the same request.ESCALATION_REQUIRED
- Send the same purchase twiceOne payment, not two.same decision_id
- Revoke the agent mid-taskThe next call is refused.AGENT_NOT_ACTIVE
- Tell the agent to ignore its limitsNothing changes: the limits live in Regent, not in the agent.deny, as before
- Verify a receipt yourselfValid. Change one character and it fails.pip install regent-receipt-verify
Found a way for an agent to spend without a decision? That is the most useful report you can send us. Tell us how you did it.
The beta, plainly
- Free for three months
- Sandbox for 30 days, then go live, free for three months in total from the day you sign up. Regent never asks for a card to use Regent itself. What comes after is on the pricing page, and the launch price there stays yours for twelve months after your beta ends. During the beta every feature is available on every account.
- Test money first
- A new account is a sandbox: Stripe in test mode, test USDC, and at most $100 per payment. It lasts 30 days; going live keeps everything you built in it.
- Real money needs a verified owner
- You verify your identity once. Then you can connect your own Stripe account or your own card. Card purchases through Agentcard need a US card and an owner aged 18 or over.
- We never hold your money
- Payments run on your Stripe account, your card or your wallet. Regent decides; the payment provider moves the money.
- What we see
- Amounts, merchants, your limits and every decision. Never your card number. Identity documents stay with the verification provider.
- It is a beta
- Offered by Regent Protocol Inc., a Delaware corporation. Things will change and some will break. We fix fast and write down what changed. See the terms and the privacy policy.
What beta participants get
- Launch pricing locked for 12 months
- After your beta ends, and written into our Terms of Use, section 6.2. Applies to accounts created on or before January 11, 2027.
- Early access to new capabilities
- As they ship.
- A direct line to the founders
- Write to beta@regentprotocol.org, mention you're a beta participant, and a founder answers within a day.
- A founding-tester mention
- On our thanks page, only if you explicitly say you'd like one.
Tell us what happened
One short report after you try it is all we ask. Good, bad or confusing: all of it helps.
- What helps most
- The decision ID (dec_…) and the answer code your agent got back. Ask your agent for them if it did not show you.
- Never send a key
- Not to us and not to your agent. Anything in the text that looks like a key is removed before a person reads it; we cannot do that for a picture.
- Spent without a decision?
- Say so in the first line. That report goes to the top of the list.
- Prefer a chat?
- Write to info@regentprotocol.org or read the page for agents.