Let your agent pay.You stay in control.
Your agent can find and pay for online services. Every purchase is checked against your rules first: one limit, one pause switch, one receipt trail.
One URL.
Any agent.
Add Seedhape to Claude, ChatGPT, Codex, or any MCP client. Then hand your agent the SKILL.md guide so it follows the setup checklist and your rules.
https://www.seedhape.com/mcpConnecting signs in your account. It does not let anyone spend. That still needs the spending limit you set.
- 01
Add the server from a terminal:
claude mcp add --transport http seedhape https://www.seedhape.com/mcp
- 02
Run /mcp inside Claude Code and authenticate in the browser.
- 03
Ask the agent to call spending_status to confirm the tools work.
Three parties.
One boundary.
Seedhape sits between an agent's intent and settlement. People set the rules, agents act inside them, merchants get paid directly.
Set the rules once
Sign in with Google, choose how much your agent can spend per week, and you're done. Add limits per purchase, per merchant, or by date whenever you want.
- Budget per day, week, or month
- Pause or disconnect every agent instantly
- Receipts and CSV statements
Act through one connection
Claude, ChatGPT, or any MCP client connects to one endpoint and gets tools to discover, quote, pay, and prove it.
discover_offersquotepaypurchase_receiptspending_statuspause_spendingProtect your service. Get paid.
Let agents buy from your service. Payment goes directly to your wallet, with a record showing the buyer approved it.
SELL TO AGENTS ↗Try to break
your own limits.
Every purchase intent hits the same gate the runtime enforces: pause switch, merchant boundary, per-purchase limit, and period budget. Drag the rules and watch what gets through.
- PAUSED0
- MERCHANT0
- OVER LIMIT0
- BUDGET0
Every payment has
exactly one ending.
Seven durable states from intent to receipt. Every failure path releases or reconciles the reservation, so a lost response never becomes a double charge.
createdreservedsigningsubmittedfacilitator_pendingchain_pendingsettled
Intent captured
The agent asks to buy. Seedhape records who, what, how much, and for which mandate.
failedReservation released. Nothing charged.expiredAuthorization window closed. Budget returned.reconciliation_requiredLost response? Held, reconciled, never paid twice.One control plane.
Every agent rail.
Seedhape includes adapters for seven agent-commerce protocols. You get one buyer experience while the payment runtime picks the rail. Each badge shows the live status reported by this deployment.
Checking which protocols are active on this deployment…
See it
in motion.
This short demo shows how Seedhape keeps every purchase visible and under your control.
READ THE DOCS ↗From a simple ask
to a safe outcome.
See what bounded, user-approved agents can do across everyday purchases and software work.
Get me to the show
An agent plans the evening, finds tickets and dinner, and asks before spending.
Ship by morning
A coding agent finds the tools it needs while Seedhape enforces the developer’s purchase rules.
Everything your agents did.
Nothing hidden.
Payment activity
Sign in to view activity
Activity is private to your Seedhape account. Choose Google or MetaMask from the same sign-in dialog.
Market signal brief
This paid service returns its report after the buyer approves the price. Payment goes directly to the seller.
Optional service escrow
Fund, deliver, release, or dispute through an independent service agreement, with an arbitrator both sides choose before funding.
Agent identity
Verified agent profiles with signed exchanges and reviews.