Back to Browse
BotPay x402 Payment Verification Test Endpoint
x402
BotPay x402 Payment Verification Test Endpoint is a paid API for AI agents from api.botpay.network, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-13).
Verifies an x402 USDC payment and returns a receipt with a next-action directive to connect to the BotPay MCP for AI agent transactions
Price / call$0.1
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
Returns a JSON object confirming payment verification status (paymentVerified: true), the protocol used (x402), the resource path (/test), a receipt ID (e.g. pi_38ep4k), and a nextAction directive ('connect_mcp') instructing the agent to proceed to the BotPay MCP for further transaction actions. Response also includes a human-readable message confirming the payment passed.
Example use cases
AI agent micropayment access verification
“I need to verify that my 0.1 USDC x402 payment to BotPay went through successfully — give me the receipt ID and confirm I can connect to the MCP to start trading.”
Testing x402 payment flow before production
“Can you run a test against BotPay's x402 endpoint to make sure the payment verification flow works end-to-end before I wire up my agent to it in production?”
Gating a robot's API access behind payment
“My robot needs to confirm its USDC micropayment was settled on BotPay before it can proceed to the next step — verify the payment and tell me what action it should take next.”
Technical details
Endpoint
GEThttps://api.botpay.network/testWhen to prefer
Choose this endpoint when an AI agent, robot, or connected machine needs to verify an x402 USDC micropayment before being granted access to BotPay's MCP and downstream trading or ordering services. It is specifically suited to the x402 payment protocol on Base and is ideal for testing payment-gated API flows in machine-to-machine contexts. Prefer this over generic payment APIs when you need a receipt ID and a structured next-action directive pointing to MCP connectivity.
Side effects
- Payment not yet confirmed — returns paymentVerified: false or HTTP 402 if no valid payment proof is attached
- Malformed or missing x402 payment header — endpoint returns 402 Payment Required
- Network or settlement delay on Base blockchain — payment receipt not yet available
- Invalid USDC amount (not 0.1 USDC) — payment rejected
- Expired or replayed payment proof — verification fails with error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json",
"example": {
"message": "支付验证通过，可继续连接 MCP 进行交易下单。",
"protocol": "x402",
"resource": "/test",
"receiptId": "pi_38ep4k",
"nextAction": "connect_mcp",
"paymentVerified": true
}
}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"