In a nutshell
AI agents can pay for APIs and data per request, in stablecoins, through open agent payment protocols. If you sell to agents, a Blockradar address can receive those payments. They arrive as ordinary deposits, with the usual webhook and the paying agent’s wallet as the sender, so there is nothing new to integrate on the Blockradar side.
AI agents can pay for APIs and data per request, in stablecoins, through open agent payment protocols. If you sell to agents, a Blockradar address can receive those payments. They arrive as ordinary deposits, with the usual webhook and the paying agent’s wallet as the sender, so there is nothing new to integrate on the Blockradar side.
Supported Protocols
Prerequisites
1
API Key
Get your API key from the Blockradar Dashboard. Navigate to Developers to generate one.
2
EVM Master Wallet
Create a master wallet in the dashboard on the chain you charge on, such as Base (see Create a Master Wallet).
3
USDC Enabled
Enable USDC on the wallet. Your wallet only detects deposits for assets you have added. See Asset Management.
4
Webhook URL
Configure a webhook endpoint in your dashboard under Developers → Webhooks to be notified of each payment.
How x402 Works
x402 is an open protocol that lets an API charge per request. Your API answers an unpaid request with HTTP402 Payment Required and the price, the agent retries with a signed USDC authorization, and a facilitator verifies that authorization and submits the transfer on-chain, paying the gas. The USDC moves straight from the agent’s wallet to your payTo address.
You run the x402 server middleware and choose the facilitator. Blockradar is where the money lands.
Get Paid with x402
1
Set a Blockradar address as payTo
Use the master wallet’s address, or generate a child address per product or customer and attach
metadata so each payment maps back to what was bought. On the Checkout plan, child addresses are not available, so use the master wallet’s address.2
Settle through a facilitator
Point your x402 middleware at a facilitator that supports your network. Circle’s Facilitator Service settles USDC on Arc, Base, and Polygon PoS. Use a Circle API key when configuring it. For Solana, use a facilitator that supports Solana.
3
Receive the payment as a deposit
When the facilitator settles, the USDC transfer to your
payTo address is detected like any other deposit and fires the usual deposit.success webhook.senderAddress is the buyer’s wallet, not the facilitator that submitted the transaction, so you can see who paid. hash matches the transaction in the PAYMENT-RESPONSE your server returned.
Receiving x402 on Solana
On Solana, the agent signs a USDC transfer and the facilitator pays the network fee. The payment arrives the same way: adeposit.success webhook with the agent’s wallet as senderAddress, not the facilitator that paid the fee.
How MPP Works
MPP (Machine Payments Protocol) is another open protocol for paying per request over HTTP. Its EVM charge settles the same way as x402: the agent signs an EIP-3009 USDC authorization to yourrecipient address, your server submits it on-chain, and the USDC moves straight from the agent’s wallet to that address. The headers differ (WWW-Authenticate: Payment, Authorization: Payment and Payment-Receipt), but the deposit Blockradar records is the same.
Get Paid with MPP
1
Set a Blockradar address as recipient
MPP calls the receiving address
recipient. Use a Blockradar address exactly as you would for x402 payTo, including the same Checkout plan rule.2
Settle through a facilitator
The official
mppx server settles EVM charges through an x402 facilitator, so the facilitator you use for x402 works here too.3
Receive the payment as a deposit
The settled transfer fires the usual
deposit.success webhook, with the agent’s wallet as senderAddress.JavaScript
reference in the Payment-Receipt your server returns is the on-chain transaction hash, and it matches the deposit’s hash. The sweep tip above applies to MPP payments too.
Get Paid with MPP on Tempo
An MPP charge on Tempo is a direct stablecoin transfer to yourrecipient address, carrying a memo that ties it to the challenge. The agent or your server broadcasts it, so no facilitator is involved.
1
Enable the token on your Tempo wallet
Your wallet only detects deposits for assets you have added. See Asset Management.
2
Set a Blockradar Tempo address as recipient
Use your Tempo master wallet’s address or a child address (the master wallet’s address on the Checkout plan), and set
currency to the token you want to receive: OUSD, USDC.e or USDT. Their addresses are in the example below. USDT shows as USDT0 on-chain.3
Receive the payment as a deposit
The transfer fires the usual
deposit.success webhook, with the agent’s wallet as senderAddress.JavaScript
feePayer to tempo.charge(). Use a key held on your own server, not your Blockradar address: the fee payer co-signs each charge transaction, and Blockradar cannot co-sign Tempo fee-payer transactions.
Limitations
- EVM networks and Solana only. Payments on other networks are not supported.
- MPP sessions on Tempo are coming soon. Until then, session settlements are not supported.
- Circle Gateway nanopayments land in a Gateway balance. Circle settles these batched sub-cent payments into the seller’s Gateway balance, not as an on-chain transfer to
payTo, so they do not arrive as Blockradar deposits and are out of scope for this guide.
Best Practices
- One address per product or customer. Generate a child address per paid resource or per buyer account and tag it with
metadata, so every deposit webhook tells you what was bought without a lookup. - Reconcile by hash. Match each
deposit.successwebhook’shashto thetransactioninPAYMENT-RESPONSE(x402) or thereferenceinPayment-Receipt(MPP). - Test on testnet first. Point your middleware at a testnet network, such as Base Sepolia (
eip155:84532), and pay yourself with testnet USDC from the faucets before going live.

