FAQ
Questions?
We have answers.
Everything you need to know about agent payments, wallets, and controls on ampersend.
General
ampersend is a management platform for agent payments and operations. It gives agents a wallet to spend from, and gives you a dashboard to see exactly what they're doing with it. It gives you observability, automation, and guardrails on agent payments.
- Enterprises that need compliance-ready, auditable agent infrastructure
- People running OpenClaw, Hermes or similar agents to automate their work or life
- AI startups running fleets of agents that need to pay for services, APIs, or each other
- Agents offering their services on marketplaces
- Developers building with Google ADK, LangChain, CrewAI, LangGraph, or any agent framework
- Anyone who needs agents to transact autonomously, without losing visibility or control
- Give your agents a wallet that allows them to spend on any x402-enabled vendor, and buy prepaid cards to do credit card payments
- Load your agent wallets with a credit card, bank account or stablecoins
- Set spend limits (daily, monthly, per transaction) per agent
- Configure an allowlist of who your agent is allowed to transact with
- Set up auto top-up rules so agents always have funds available, within budgets you control
- See every transaction in real time — what was paid, to whom, why
- Configure auto collection rules so any money earned by your agents is automatically sent where it needs to be (your stablecoin wallet or bank account — coming soon)
- [Coming soon] Role-based access for team members managing agent fleets
- [Coming soon] Export logs for compliance and reporting
ampersend is built by a team within Edge & Node, the founding team behind The Graph.
Sign up at app.ampersend.ai or ask your agent to install ampersend.ai/skill.md. You'll get a wallet, a dashboard, and everything you need to start having control over your agents.
Wallet & Payments
ampersend uses Safe smart accounts. One main account, plus a separate smart account for each agent. All of these are powered by a Coinbase Developer Platform (CDP) embedded wallet that you own, tied to your user account.
CDP wallets use MPC and are managed by Coinbase, but they're self-custodial: Coinbase cannot move funds without your consent, and you can export the private key at any time from the user menu.
Auto top-up and auto collect use custom smart account modules. Your CDP wallet pre-authorizes the specific transfer configuration you allow, and ampersend's infrastructure triggers it, but only the exact transfer you've permitted.
Agent keys (what your agents actually use) are EOAs added to a custom “cosigner validator” module on the smart account. They can sign transactions on the agent account, but those signatures must be co-signed by an ampersend server key — which means neither the agent nor ampersend can move funds unilaterally. The server key enforces the policies you define in the dashboard.
The bottom line: you can export the private key that owns all of these accounts. Neither ampersend nor Coinbase can move your funds without your involvement.
Yes. ampersend works both sides of the transaction.
If your agent offers a service — answering queries, running tasks, providing data, or executing workflows — it can accept payments from other agents or users via x402. You get a payment address for your agent, and ampersend tracks every inbound payment with the same observability and reporting as outbound spend.
This means you can build agents that earn by doing work, and spend those earnings on the resources they need to do more of it. ampersend handles the full cycle: receive, hold, and spend with the controls and audit trail you'd expect.
No. ampersend doesn't move money — it manages the rules around how agents move money using x402 and other settlement primitives. Think of it less like a payment processor and more like a treasury and control layer.
Any service available on our marketplace, as well as anything built on x402 (check out x402 Bazaar for a growing list of supported vendors). Prepaid card support is coming soon, which will open up credit card payments too.
Integrations & Protocols
ampersend supports A2A, MCP, and HTTP. For payments, it uses x402, Coinbase's protocol for instant stablecoin settlement baked directly into HTTP requests.
Whichever protocol your agents use, ampersend sits on top as the management layer, keeping transactions authorized, tracked, and auditable.
x402 is a payment protocol built by Coinbase that lets agents pay for things over HTTP using stablecoins. No checkout flow, no API key billing, just instant settlement baked into the request itself.
A2A (Agent-to-Agent) is Google's framework for agents to communicate directly with each other, delegating tasks, sharing context, coordinating work.
ampersend connects these two: when agents talk via A2A and need to pay via x402, ampersend is the control plane that makes sure those transactions are authorized, tracked, and auditable.
No. ampersend's CLI and SDK mean we support most agent frameworks out of the box. If you're not sure whether your setup is compatible, reach out to ampersend@edgeandnode.com and we'll answer any questions.
Yes. ampersend supports A2A, MCP, and plain HTTP, so you're not locked into any one communication protocol. Credit card payment support is also coming soon.
Access & Pricing
No. You can add funds directly in the ampersend UI using Coinbase, so you don't need to hold or manage crypto yourself to get started.
Not for the main platform. Some features like onramp/offramp and certain card options may require identity verification, but you can get started without it.
It's free during the beta period. Pricing will be announced soon and there will be a free tier. If you have questions in the meantime, just reach out to ampersend@edgeandnode.com.
Community & Support
There is a feedback form within ampersend, or feel free to email direct at ampersend@edgeandnode.com.
Yes — please join our Telegram builders community: @ampersendbuilders.