Sign in
Choose Google for managed onboarding or MetaMask for wallet-native identity. Seedhape creates or reuses your mapped agent address, but sign-in alone never grants payment authority.
SIGN IN ON HOME ↗START HERE / USER GUIDESign in → authorize → pay safely
Your first
agent payment.
Follow this path to give an agent a bounded wallet, connect it to Claude or ChatGPT, make a controlled purchase, and take the authority back.
01 / THE CHECKLISTOne action
One action
at a time.
Do not skip the review points. Preparation creates a proposal; only an explicit mandate or payment signature authorizes value movement.
Create an agent mandate
Open authorization, choose the payment rail, set the purpose, per-payment cap, period budget, payment count, allowed hosts, and expiry. Review the exact EIP-712 message and sign it in MetaMask, or confirm the managed Google authorization.
AUTHORIZE AGENT ↗Fund the agent wallet
Open the funding page and use the displayed mapped agent address. Buy Base USDC with thirdweb or transfer USDC directly. The agent needs USDC for EIP-3009; the sending wallet needs Base ETH for a direct transfer.
FUND AGENT ↗Connect Claude or ChatGPT
Create an MCP token or start the hosted OAuth connection. Add the Seedhape MCP endpoint to your client and complete the browser consent flow. The client receives access scoped to your Seedhape account.
CONNECT MCP ↗Find and pay from chat
Ask the agent to discover an available service, inspect its price and payment requirements, prepare checkout, and pay only when the request fits your active mandate. Review every approval prompt.
SEE CHAT EXAMPLES ↗Review and revoke
Use mandate management to inspect the policy, agent balance, and activity. Revoke the Seedhape mandate when you are finished; also revoke any MetaMask ERC-7710 permission in MetaMask for an on-chain hard stop.
MANAGE MANDATES ↗02 / MCP CLIENTSConnect the
Connect the
conversation.
Claude and ChatGPT use the same Seedhape MCP endpoint. Their settings labels can change; the security model does not.
Connect Claude
- Open Claude’s connector or MCP settings.
- Add the Seedhape MCP server URL shown on Connect MCP, normally
https://www.seedhape.com/mcp. - Complete the browser OAuth consent flow, or paste the one-time bearer token if your client asks for manual credentials.
- Return to Claude and confirm that the Seedhape tools are available.
Try: List the available Seedhape services and show each price, network, and payment method. Do not pay yet.
Connect ChatGPT
- Open ChatGPT’s Apps, Connectors, or MCP settings.
- Add the Seedhape MCP endpoint and start authorization.
- Sign in through the Seedhape browser page and approve only the requested MCP connection.
- Return to ChatGPT and verify the Seedhape tools before requesting a purchase.
Try: Find a service that can provide a market signal. Compare the options and ask me before any payment.
03 / USE IT IN CHATDiscovery first.
Discovery first.
Payment second.
The agent can explore freely, but payment must remain inside the signed boundary. Use explicit instructions when you want a purchase.
“Find the available paid services for weather and market data. Show the merchant, resource, price, asset, network, and recipient.”
“Prepare the cheapest market-signal option, but do not pay. Explain what mandate and payment method would be used.”
“If the request is within my active mandate, show me the final amount and merchant, then ask for confirmation before paying.”
“After payment, show the settlement transaction, receipt, resource returned, and remaining mandate allowance.”
04 / HOW IT WORKSThe technical
The technical
boundaries.
These concepts work together to keep agentic commerce useful, inspectable, and bounded.
HTTP payment negotiation
A merchant returns HTTP 402 with the exact asset, amount, network, recipient, and payment method it accepts. Seedhape checks that quote before a wallet provider signs anything.
Human-defined policy
A mandate commits the purpose, host/resource boundary, per-transaction cap, period budget, payment count, asset, network, and expiry. It is the policy envelope the agent cannot exceed.
Execution address
This is the persisted address used for funded EIP-3009 execution. It is created or reused at sign-in and does not gain authority until an active mandate exists.
Gasless USDC authorization
The agent signs a USDC transfer authorization for the exact merchant payment. The facilitator submits and settles it; the agent wallet needs USDC but does not need Base ETH to sign or settle.
Delegated wallet execution
MetaMask can grant a bounded periodic permission for a smart account. This can spend from the connected user account, so it is separate from funded-agent EIP-3009 execution.
Agent tool connection
Model Context Protocol exposes structured catalog, quote, mandate, wallet, and payment tools to Claude, ChatGPT, and compatible clients. The MCP token identifies the Seedhape account; it is not a payment mandate.
Auditable payment context
Seedhape can issue an AP2 mandate/payment bundle that records what was authorized and connects the human intent, merchant quote, and settlement evidence.
Take authority back
Revoking a Seedhape mandate blocks future payments through that policy. For ERC-7710, also revoke the underlying MetaMask permission to create an on-chain hard stop.
Finished testing?
Review your spend history, revoke the mandate, and remove any MCP token or MetaMask permission you no longer need.