Back to Browse
x402 PayTo EIP-55 Diagnostic
x402
x402 PayTo EIP-55 Diagnostic is a paid API for AI agents from openclawproductions.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-11).
Returns a paid diagnostic JSON payload for the PayTo EIP-55 SKU, testing x402 payment flow with EIP-3009 authorization extras via OpenX402 facilitator.
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 ('paytoeip55'), a human-readable title ('PayTo EIP-55'), price ('$0.02'), and a diagnostic note confirming the paid response shape. Unpaid requests receive HTTP 402 with EIP-3009 payment authorization extras instead.
Example use cases
Pre-launch x402 payment wall check
“Before I launch my API, can you probe https://myapi.example.com with a GET request using the PayTo EIP-55 x402 diagnostic to confirm it returns a proper 402 with the right eip3009 payment extras?”
EIP-3009 extras format verification
“I need to verify that my x402-gated endpoint at https://staging.myservice.io is sending back the correct eip3009 authorization extras in the 402 response — can you run a PayTo EIP-55 diagnostic check against it using GET?”
Debugging x402 SKU misconfiguration
“My x402 PayTo EIP-55 setup doesn't seem to be responding correctly — can you run the paytoeip55 diagnostic against https://openclawproductions.com to see what the paid JSON payload looks like and whether the SKU and price fields are coming back right?”
Technical details
Endpoint
GEThttps://openclawproductions.com/api/v1/paytoeip55?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to test, validate, or diagnose an x402 payment-gated API endpoint specifically using the PayTo EIP-55 SKU and the OpenX402 facilitator. It is ideal for confirming that HTTP 402 responses include correct EIP-3009 authorization metadata, verifying the paid JSON response shape, or debugging x402 integration before production deployment. Prefer this over generic HTTP probers when the x402 protocol and EIP-3009 payment extras are the specific subject of investigation.
Side effects
- HTTP 402 returned if payment has not been made — expected behavior for unpaid requests, includes eip3009 payment extras
- Invalid or unreachable URL provided returns an error or empty diagnostic
- Non-GET/HEAD/DELETE HTTP methods rejected by input schema validation
- OpenX402 facilitator unavailable causes payment authorization to fail
- Malformed origin/url query parameter results in probe failure
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object | |
| inputSchema | object |
Output
Schema · Response
{
"type": "json",
"example": {
"sku": "paytoeip55",
"note": "Example paid JSON shape. Not a live settle.",
"price": "$0.02",
"title": "PayTo EIP-55"
}
}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"