Back to Browse
x402-tools Pay-to-Health Diagnostic
x402
x402-tools Pay-to-Health Diagnostic is a paid API for AI agents from openclawproductions.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-10).
Returns x402 payment-gated health diagnostics for the OpenX402 facilitator, requiring a $0.03 USDC micropayment via EIP-3009; unpaid requests return HTTP 402 with structured payment challenge extras.
Price / call$0.03
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 response containing x402 diagnostic health data including facilitator status, EIP-3009 payment extras, and confirmation that the payment flow completed. If payment was not provided, returns HTTP 402 with a structured payment challenge including the required USDC amount and EIP-3009 authorization parameters.
Example use cases
End-to-end x402 payment flow test
“Can you run the x402 health diagnostic for my wallet 0xDe12345678901234567890123456789012345678 so I can confirm my EIP-3009 payment setup is working with the OpenX402 facilitator?”
Debugging a rejected micropayment
“My x402 payments keep getting rejected — can you probe the pay-to-health endpoint using settlement address 0xFa98765432109876543210987654321098765432 and show me what the 402 challenge response looks like?”
Verifying facilitator is live before launch
“Before I go live, I need to confirm OpenX402 is up and accepting payments — run the diagnostics check with settlement address 0xBb11223344556677889900aAbBcCdDeEfF001122 and tell me the health status.”
Technical details
Endpoint
GEThttps://openclawproductions.com/api/v1/paytohealth?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you specifically need to test or diagnose the x402 payment protocol flow using the OpenX402 facilitator, particularly when validating EIP-3009 authorization, confirming a settlement address is correctly configured, or debugging why micropayments are being rejected. Not suitable for general health checks unrelated to x402 payment mechanics.
Side effects
- HTTP 402 returned when payment header is missing or invalid — expected behavior for unpaid requests, includes EIP-3009 challenge extras
- Invalid or malformed payTo address causes a 400 bad request error
- OpenX402 facilitator unavailable returns a 5xx error
- Network timeout if the facilitator is temporarily unreachable
- Payment amount mismatch (not exactly $0.03 USDC) causes payment rejection
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object | |
| inputSchema | object |
Output
Schema · Response
{
"type": "json",
"example": {
"sku": "paytohealth",
"note": "Example paid JSON shape. Not a live settle.",
"price": "$0.03",
"title": "PayTo Health"
}
}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"