Back to Browse
x402-tools Accept Bomb Diagnostic Endpoint
x402
x402-tools Accept Bomb Diagnostic Endpoint is a paid API for AI agents from openclawproductions.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-10).
Returns a paid JSON diagnostic payload ('Accept Bomb') for testing x402 payment protocol flows, requiring $0.02 USDC via EIP-3009 before serving the response.
Price / call$0.02
Success—
StatusUnknown
How this service works
Paid x402 diagnostics. Unpaid paid-SKU requests return HTTP 402 with eip3009 extras. Facilitator: OpenX402 only.
Output
A JSON object containing the SKU name ('acceptbomb'), a descriptive note, the price ('$0.02'), and the title ('Accept Bomb'). Without valid payment, returns HTTP 402 with EIP-3009 payment extras describing what authorization is required.
Example use cases
Validate x402 integration before production
“Test the Accept Bomb paid endpoint to make sure my x402 payment integration is working end-to-end — I need to confirm EIP-3009 authorization succeeds and the paid JSON payload comes back correctly.”
Debug HTTP 402 payment-gated responses
“Hit the acceptbomb diagnostic endpoint without a valid payment token so I can inspect what the 402 response and EIP-3009 extras look like when payment is missing.”
Confirm OpenX402 facilitator is live
“Probe the x402 Accept Bomb SKU to verify the OpenX402 facilitator is processing $0.02 USDC micropayments correctly and returning the expected diagnostic JSON.”
Technical details
Endpoint
GEThttps://openclawproductions.com/api/v1/acceptbomb?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to test or validate x402 micropayment protocol flows, specifically EIP-3009 USDC payments via the OpenX402 facilitator. Prefer this over generic REST diagnostic endpoints when your goal is to verify payment-gated API mechanics, inspect 402 response shapes, or confirm a live facilitator is processing on-chain micropayments correctly.
Side effects
- HTTP 402 returned when no valid EIP-3009 payment token is provided, with payment extras in response headers
- Facilitator rejection if payment is not routed through OpenX402
- Invalid or malformed payment token causes authorization failure
- Network timeout if facilitator is unreachable
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json",
"example": {
"sku": "acceptbomb",
"note": "Example paid JSON shape. Not a live settle.",
"price": "$0.02",
"title": "Accept Bomb"
}
}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"