AI agents pay for APIs, tools, data feeds, and web content through a challenge-and-response loop: the service states what a request costs, the agent checks its spending policy, signs a payment authorization tied to that challenge, retries the request, and the service or a facilitator verifies and settles the payment before releasing the result. The quoted price is only one part of the final cost; network, wallet, facilitator, cloud, and seller charges may also apply. A failed settlement should withhold the paid resource, while refunds depend on the merchant’s application-level rules rather than on a universal protocol guarantee.
The payment loop an AI agent follows
A normal API call assumes that authentication proves who the caller is and that billing happens elsewhere. A paid agent request combines those jobs at request time. The agent may have no human-operated checkout screen, so the server must return machine-readable terms that software can evaluate safely.
As an Amazon Associate I earn from qualifying purchases.
- Request: The agent asks for an API operation, tool execution, data record, or protected page.
- Challenge: The server returns HTTP
402 Payment Required(or an equivalent protocol message) describing the amount, recipient, asset, network, validity window, and payment method. - Policy check: The agent compares those terms with its budget, allowed networks and assets, merchant rules, and any requirement for human approval. A policy can reject an unexpectedly large amount or an unfamiliar recipient before any signature is created.
- Authorization: The agent’s wallet signs a payment credential bound to the challenge. The signed data normally commits to the payee, amount or spending cap, asset, network, and expiry, and includes replay protection.
- Retry: The agent sends the signed proof in the protocol’s payment header or message and repeats the original request.
- Verification and settlement: The server or an independent facilitator checks the signature and challenge conditions, then submits or confirms settlement on the payment network.
- Delivery: The service releases the result only after the required checks succeed. If verification or settlement fails, the paid content should remain withheld.
This sequence separates authentication (proving that a valid wallet or credential authorized the payment) from authorization (deciding whether this particular purchase is permitted). A managed deployment can add an identity for the agent, a secret store, per-agent limits, expiry rules, and optional human approval without changing the basic loop.
x402: HTTP-native pay-per-request payments
x402 is the clearest example of payment at the point of an HTTP request. Its stated goal is to make programmatic commerce permissionless and developer-friendly. The service uses the previously unused HTTP 402 status to advertise payment requirements, and the client retries with a signed payment payload.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
What an x402 exchange contains
In x402 version 2, the transport defines three objects: PAYMENT-REQUIRED carries the server’s requirements, PAYMENT-SIGNATURE carries the client’s signed authorization, and PAYMENT-RESPONSE reports verification or settlement results. The requirement can identify the exact price, recipient, token or other asset, network, and scheme. A client must treat those fields as untrusted input until its own policy approves them.
The protocol supports extensible payment schemes. An exact scheme charges the specified amount for the request. An upto or metered design can authorize spending up to a cap and charge according to measured use. Batch settlement can group several authorizations for later submission. Availability of a scheme still depends on the network, wallet, server implementation, and client library; x402 does not make every combination universally available.
Who verifies and settles
The merchant can verify and settle directly, or delegate those operations to a facilitator. Verification checks that the signature is valid, the authorization matches the challenge, the credential is within its validity window, and the payment has not already been used. Settlement submits or confirms the transfer and returns a result that the server can use before delivering the resource. The protocol leaves client-side budget management to the application, so an implementation must supply its own limits, approval logic, and key protection.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsDashboard figures are not market statistics
The x402 Foundation site displayed 75.41 million transactions and $24.24 million in volume when accessed on October 15, 2026. Those are volatile, platform-reported dashboard snapshots, not an independently audited measure of the entire agent-payment market.
Rank #2
- Proven security at scale: Over 9 years and millions of cards issued with no known remote hacks, while military‑grade EAL6+ security keeps your private keys locked inside the chip. Your cryptocurrencies stay strongly protected from online attackers.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 14,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Smart backup: Use your second Tangem Wallet as your Backup keys with end‑to‑end encryption; no more papers, pictures. If one card is lost, the remaining can still restore full access, with an optional seed phrase available for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide (4.9 App Store, 4.8 Google Play) - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
MPP: the same status code, different message semantics
MPP (Machine Payments Protocol) also uses HTTP 402, but it follows standard HTTP authentication semantics. The merchant responds with WWW-Authenticate: Payment. The agent obtains a signed payment credential and retries with Authorization: Payment.
One-time charges and metered sessions
MPP documentation distinguishes one-time charges from capped metered sessions. A one-time credential authorizes a single purchase. A session can authorize repeated or measured use up to a stated cap, allowing a service to bill for consumption while limiting the maximum exposure. The cap, expiry, and measurement rules must be explicit so the agent can evaluate them before signing.
How to compare MPP and x402
| Question | x402 | MPP |
|---|---|---|
| Initial challenge | PAYMENT-REQUIRED object in the x402 v2 transport |
402 Payment Required with WWW-Authenticate: Payment |
| Retry credential | PAYMENT-SIGNATURE |
Authorization: Payment |
| Result message | PAYMENT-RESPONSE reports verification or settlement |
Authentication response semantics defined by the MPP implementation |
| Payment models described in the supplied specifications | exact, upto, and batch-settlement schemes |
One-time charges and capped metered sessions |
| Budget ownership | Client application manages spending policy | Agent or its managed host must enforce caps and expiry |
Both protocols require a client to check the payee, amount or cap, asset, network, expiry, and replay conditions. Their headers and settlement implementations are not interchangeable merely because both use status code 402. When selecting one, also check supported networks, who operates verification and settlement, how identity is disclosed, and the maturity of the relevant specification.
Managed payment orchestration with AWS AgentCore Payments
A managed service can package protocol handling so an agent does not have to implement wallet plumbing, token retrieval, and policy enforcement itself. AWS AgentCore Payments can orchestrate x402 or MPP, enforce per-session spending limits and expiry, and retrieve a payment token through GetResourcePaymentToken. It can integrate embedded wallets from Coinbase CDP or Stripe (Privy), subject to the deployment’s configuration and supported networks.
Rank #3
- Seedless by design, nothing to steal: Your private key is generated inside the EAL6+ chip and never leaves it. No seed phrase is shown or typed at setup, so a tampered device, keylogger, or phishing site has nothing to capture. 9+ years, millions of card.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 16,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Backup without a seed phrase: Your wallet is copied to 2 backup cards with end-to-end encryption, so there are no words on paper to lose or leak. Keep them in separate places; if one card is lost, the others restore full access. Optional seed phrase for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
What the managed layer adds
- Identity and secrets: credentials and wallet keys can be kept in managed storage rather than in an agent prompt or source file.
- Policy: per-agent or per-session caps, allowed resources, and expiry can be enforced outside the model’s reasoning loop.
- Approval: deployments can require a human or supervisory service to approve selected transactions.
- Failure accounting: AWS documentation states that a failed signing operation after budget deduction does not deduct the failed payment.
These controls reduce implementation work but do not make the merchant’s price, network fees, or refund policy disappear. The operator still needs to decide which assets and networks are acceptable and what happens when an operation runs but settlement later fails.
What an AI agent actually pays
The amount in the payment challenge is the seller’s stated price for the resource. The final debit can include several additional components:
- Seller price: the amount quoted in the challenge for the API call, tool, data, or page.
- Network fee: a blockchain or payment-network charge for confirming the transfer.
- Wallet or facilitator charge: an embedded-wallet provider or settlement facilitator may add a fee.
- Cloud-service charge: a managed orchestration service can bill separately for its infrastructure or API usage.
The x402 website describes the protocol itself as free for customer and merchant, with nominal payment-network fees. That is a protocol-fee statement, not a promise of zero total cost: a particular network can charge more, a wallet or facilitator can add its own price, and the seller can set any resource fee it chooses.
Why tiny payments are difficult for traditional rails
AWS explains that traditional payment systems often impose minimum fees that make transactions below $0.01 uneconomic. Stablecoins and HTTP-native payment protocols target this gap by allowing software to authorize small amounts without a human checkout. The threshold is an economic observation, not a universal rule; the break-even point varies with the network, provider, currency, and transaction volume.
Rank #4
- EAL5+ CERTIFIED SECURE ELEMENT + FINGERPRINT PROTECTION — Your private keys stay encrypted offline on a certified EAL5+ chip, the same security tier used in EMV bank cards. Built by DCENT, securing crypto since 2018. Fingerprint authentication adds a second layer no PIN-only wallet can match.
- 10,000+ ASSETS NATIVE ON 100+ BLOCKCHAINS — Hold Bitcoin, Ethereum, XRP, Solana, Cardano, popular stablecoins (USDT, USDC), and NFTs in one wallet. No third-party apps, no fragmented setup — every supported asset works straight out of the box.
- TAP-TO-SIGN MOBILE EXPERIENCE — Pair your wallet with the DCENT mobile app over Bluetooth. Manage tokens, review transactions, and access in-app swap features directly from your phone — no cables, no desktop required.
- WEB3 & dAPP ACCESS VIA METAMASK — Connect to MetaMask and other browser extension wallets to manage NFTs, claim airdrops, and access dApps. A large screen and intuitive 4-button interface keep every transaction clearly visible before you sign.
- SEAMLESS FIRMWARE UPDATES & 30-DAY MONEY-BACK GUARANTEE — Apply security updates without resetting your wallet or migrating funds. Backed by Amazon's 30-day money-back guarantee — your purchase is risk-free.
A proposed percentage is not a universal rate
An AEPP Internet-Draft published in 2026 proposes a micro-fee of no more than 0.4% per execution. It is a draft design, not a binding rule for x402, MPP, AP2, or every provider. No authoritative source establishes a universal industry-average fee or refund rate.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How payment authentication protects the agent and merchant
A payment credential should be cryptographically signed and challenge-bound. Binding prevents a signature intended for one purchase from being copied to another request. A robust credential covers:
- the exact amount or maximum cap;
- the recipient or merchant identifier;
- the asset and network;
- the resource, request, or session being authorized;
- an issuance time and expiration time;
- a nonce, request identifier, or other replay-resistant value.
The signature proves authorization of those terms; it does not by itself prove that the service will deliver a useful result or issue a refund. Agents should never let a model freely choose a private key, silently increase a cap, or accept a changed payee on retry. Keep signing keys in a wallet or secret manager, restrict which origins can request payment, and log the challenge, policy decision, signature request, and settlement result for audit.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Mandates and user control
AP2 approaches user authorization through cryptographically signed mandates. A mandate records the user’s instruction in a tamper-evident, accountable form that an agent can present when acting on the user’s behalf. This is an authorization pattern, not a guarantee that every merchant accepts AP2 or that a mandate overrides a merchant’s own payment rules.
Best Value
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
What happens when a paid request fails?
Verification or settlement failure
If the signature is invalid, the credential is expired, the amount exceeds policy, the nonce has already been used, or the network cannot settle the transfer, the service should return an error and withhold the paid resource. The x402 MCP transport specifies an error result when settlement fails, including a case where a tool has already run; the tool content is then withheld. That protects the merchant from unpaid delivery, but it is not a consumer-refund promise.
Signing failure before a payment is sent
A wallet may reject a signature request, lose connectivity, or hit a policy limit. In AWS AgentCore Payments, AWS documentation says a failed signing operation after budget deduction does not deduct the failed payment. Other implementations must document their own reservation and accounting behavior; an agent should not assume that a locally reserved amount has been released until it receives a definitive result.
Execution succeeds but delivery or settlement is uncertain
Distributed systems can lose a response after the merchant has executed a tool or submitted a transfer. Use an idempotency key or request identifier so a retry can query status instead of paying twice. The agent should distinguish “not submitted,” “submitted but unconfirmed,” “settled,” and “executed but content withheld.” Those states determine whether a retry is safe and whether a later refund request is appropriate.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Refunds are an application contract, not a built-in x402 guarantee
Core x402 defines payment requirements, authorization, verification, and settlement. It does not define one universal refund policy. The merchant or application must specify whether funds are captured before execution, held in escrow, charged only after metered use, or released under an upto authorization.
Questions a refund policy must answer
- Was money captured before the tool ran, or only after successful execution?
- Can the merchant issue a full or partial refund, and who is authorized to approve it?
- How long does a customer have to dispute a result?
- Which party supplies liquidity while a refund or dispute is pending?
- How is a refund identified and reconciled with the original authorization?
Agent Commerce Kit documents refund-management patterns, while a 2026 escrow-oriented research proposal describes delayed fulfilment and partial refunds. Those are higher-level designs, not evidence that every x402 or MPP service supports automatic refunds. Read the merchant’s terms before allowing an agent to spend beyond an amount the owner can tolerate losing.
A practical policy checklist for deploying an agent payer
- Allowlist counterparties: accept payment challenges only from approved origins and verify the expected recipient.
- Set hard limits: define per-request, per-session, per-agent, and daily caps; reject a challenge that exceeds any limit.
- Restrict assets and networks: permit only assets the treasury can hold and networks the wallet and facilitator support.
- Require fresh credentials: enforce expiry, nonce or request binding, and one-time use where the scheme requires it.
- Separate authorization from signing: let policy code decide whether a payment is allowed, then let a protected wallet perform the signature.
- Use idempotency: record a request identifier and query settlement status before retrying an uncertain call.
- Log every state: retain the challenge, policy decision, signature outcome, settlement response, delivery status, and any refund decision.
- Define human escalation: route unusual payees, high caps, expired sessions, and refund disputes to an operator.
How to choose between payment options
Compare implementations on the dimensions that affect both safety and economics:
- header and message semantics, including how a client discovers requirements;
- exact versus capped or metered payment models;
- supported assets, networks, wallets, and facilitators;
- who verifies and settles, and what happens during an outage;
- per-request, per-session, and expiry controls;
- replay protection and idempotency behavior;
- privacy and identity disclosure to the merchant or facilitator;
- standards maturity, governance, and the clarity of refund terms.
No single protocol answers all of these questions. x402 provides an extensible HTTP-native pattern, MPP uses familiar authentication headers and supports one-time and capped sessions, and managed services add operational controls. The safest choice is the one whose payment semantics and failure handling match the agent’s actual spending authority.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
