Back to Browse
BotPay Network Payment API
x402
BotPay Network Payment API is a paid API for AI agents from api.botpay.network, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).
Processes a micropayment of $0.01 USDC on Base network via HTTP GET, enabling pay-per-call API access through the x402 payment protocol
Price / call$0.01
Success—
StatusUnknown
How this service works
BotPay provides payment access, API discovery, automated service delivery, and settlement infrastructure for AI agents, applications, robots, and connected machines.
Output
The endpoint returns a response body (structure varies) after the $0.01 USDC micropayment on Base is confirmed via x402 protocol. On success, the agent receives the API payload plus a payment receipt. On failure, a 402 Payment Required or error status is returned.
Example use cases
Micropayment-gated bot data access
“I need to call the BotPay API to get bot-related data — go ahead and pay the $0.01 USDC fee on Base using x402 and show me what comes back.”
Automated pay-per-call agent workflow
“Set up my agent to automatically pay the $0.01 USDC BotPay toll on Base whenever it needs to hit the BotPay endpoint, so it never gets blocked by a 402 response.”
Testing x402 payment-gated API integration
“I want to test the x402 payment flow — send a GET request to BotPay, pay the one-cent USDC fee on Base, and confirm we get a successful response back.”
Technical details
Endpoint
GEThttps://api.botpay.network/pay?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to make a single pay-per-call request to the BotPay network and your agent wallet holds USDC on Base. It is specifically suited for x402-protocol-enabled agents that can attach payment headers to HTTP requests. Prefer this over free-tier alternatives when BotPay data or bot-network access is explicitly required.
Side effects
- Insufficient USDC balance on Base wallet returns 402 Payment Required
- Invalid or missing x402 payment header causes authentication rejection
- Network congestion on Base L2 causes transaction timeout
- Malformed GET request with unexpected query parameters returns 400 Bad Request
- Payment confirmed but API service unavailable returns 503
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| testRunId | string | Optional caller-supplied correlation ID. |
Output
Schema · Response
{
"type": "json",
"example": {
"message": "Receipt ID: pi_38ep4k",
"protocol": "x402",
"resource": "/pay",
"receiptId": "pi_38ep4k"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"