Back to Browse
x402 Schema Dual Diagnostics
x402
x402 Schema Dual Diagnostics is a paid API for AI agents from openclawproductions.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-11).
Returns a paid diagnostic JSON payload describing the schemadual SKU, useful for testing x402 payment flows and verifying EIP-3009 payment headers.
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
Returns a JSON object containing the SKU identifier ('schemadual'), a descriptive note clarifying it is an example paid shape rather than a live settlement, the price ('$0.03'), and the title ('Schema Dual'). When called without a valid x402 payment, returns HTTP 402 with EIP-3009 payment requirement extras instead.
Example use cases
Verify x402 payment integration
“I just wired up x402 on my API and want to confirm the full payment flow is working — can you hit the schemadual diagnostic endpoint with a GET against my origin https://myapi.example.com and show me what comes back after the $0.03 USDC payment clears?”
Debug 402 gating with EIP-3009
“My x402 endpoint keeps rejecting payments and I can't tell if it's the facilitator or my EIP-3009 auth — can you probe https://openclawproductions.com/api/v1/schemadual with a GET and show me the 402 error details including the eip3009 extras it returns?”
Inspect schemadual SKU response shape
“Can you call the schemadual SKU diagnostic via GET and show me exactly what the paid JSON response looks like, including the price, title, and SKU fields — I need to model my own paid endpoint response after it.”
Technical details
Endpoint
GEThttps://openclawproductions.com/api/v1/schemadual?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to test or debug x402 protocol payment flows, verify EIP-3009 authorization header correctness, or inspect the expected paid response shape for a schemadual SKU. It is specifically suited for developers integrating with the OpenX402 facilitator and needing a live, real-payment diagnostic endpoint rather than a mock. Prefer this over generic HTTP testing tools when you specifically need x402 payment gating behavior validated.
Side effects
- HTTP 402 returned when no valid x402 payment header is provided — includes EIP-3009 extras specifying payment requirements
- Request rejected if facilitator is not OpenX402 — only OpenX402 is supported
- Invalid method (e.g. POST, PUT) returns an error — only GET, HEAD, DELETE are accepted
- Malformed or missing 'input.type' or 'input.method' fields cause schema validation failure
- Unreachable or invalid URL/origin parameter causes probe failure
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object | |
| inputSchema | object |
Output
Schema · Response
{
"type": "json",
"example": {
"sku": "schemadual",
"note": "Example paid JSON shape. Not a live settle.",
"price": "$0.03",
"title": "Schema Dual"
}
}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"