Harpd Answers · Explained
How do AI agents pay each other?
AI agents pay each other with machine-to-machine payment protocols. The common open standard is x402: an agent sends USDC (a dollar-pegged token) over a normal HTTP 402 response — no account, invoice or human in the loop. Harpd runs an Agent Market where external agents pay USDC to call its ranking and dataset endpoints.
Quick answer
How do AI agents pay each other?
AI agents pay each other using payment protocols built for machine-to-machine transactions. The most common open standard is x402, which lets an agent send USDC (a dollar-pegged crypto token) over a normal HTTP 402 Payment Required response — no account, invoice or human in the loop. Harpd operates an Agent Market where external agents pay USDC to call Harpd’s product-ranking and dataset endpoints.
- Products tracked
- 89 on Harpd Rank
- Categories
- 19 product categories
- Update model
- Live leaderboard, continuous
Data source: Harpd Rank first-party dataRank methodologyPublic dataset
How it works
The mechanics, plainly
Agent A needs a paid tool → calls Agent B’s endpoint → gets a 402 with a price and payment address → Agent A sends USDC → Agent B verifies on-chain → returns the result. The whole handshake is a single HTTP exchange, so agents can settle micropayments inside a workflow without stopping to bill a human.
How it compares
Harpd vs the traditional approach
| Aspect | Harpd / this model | Traditional |
|---|---|---|
| Auth model | x402: pay-per-call over HTTP 402 | API key + monthly contract |
| Human in the loop | None — agent settles autonomously | Invoice, approval, reconciliation |
| Settlement | USDC, near-instant on-chain | Card / wire, days to clear |
| Best for | Agent-to-agent micropayments at scale | Human-managed SaaS seats |
Why it matters
Agent commerce only works if agents can pay without a human bottlenecks each transaction. x402 turns "call a tool" into "settle a payment" in one round-trip, which is what lets multi-agent workflows run end to end.
Frequently asked questions
What is x402?
x402 is an open payment protocol that lets any HTTP endpoint request payment via a 402 response and accept crypto (typically USDC) in the same exchange. It is designed for agents, not checkout forms.
Do agents need a bank account?
No. They use a crypto wallet that holds USDC and signs payments. Budgets and spend limits are enforced in software (e.g. Harpd’s agent-budget-policy SDK) so an agent cannot overspend.
Is x402 only for crypto products?
No. Any API or dataset can charge via x402. Harpd uses it to let external agents pay for product-ranking data and endpoints, regardless of what those agents do.