Back to Browse
x402-tools WWW Match 149 Diagnostics Endpoint
x402
x402-tools WWW Match 149 Diagnostics 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-11).
Returns a paid diagnostic JSON response for SKU 'wwwmatch149', gated by x402 micropayment ($0.02 USDC); unpaid requests receive HTTP 402 with EIP-3009 payment details.
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 identifier ('wwwmatch149'), a diagnostic note confirming the paid response shape, the price ('$0.02'), and a human-readable title ('Www Match 149'). Unpaid requests return HTTP 402 with EIP-3009 payment instruction extras instead.
Example use cases
Verify x402 payment gate behavior
“Can you hit the wwwmatch149 diagnostic endpoint and confirm that without payment it returns a proper HTTP 402 with EIP-3009 extras, and that after paying $0.02 USDC through OpenX402 I get the expected JSON back?”
Test USDC micropayment API integration
“I'm building an x402-gated API and want to test the full payment flow — probe the wwwmatch149 SKU on openclawproductions.com, pay the $0.02 USDC, and show me the diagnostic response so I can compare it to my own implementation.”
Inspect paid SKU diagnostic response shape
“Fetch the paid diagnostic result for SKU wwwmatch149 via the OpenX402 facilitator so I can see exactly what a settled x402 JSON response looks like — I need the title, note, and price fields for my documentation.”
Technical details
Endpoint
GEThttps://openclawproductions.com/api/v1/wwwmatch149?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to test, validate, or demonstrate the x402 HTTP micropayment protocol with EIP-3009 payment flows using the OpenX402 facilitator. It is purpose-built for diagnostics and integration testing of USDC-gated APIs, not for production data retrieval. Prefer it over generic REST endpoints when your goal is to verify 402 paywall behavior, inspect paid response shapes, or confirm facilitator compatibility.
Side effects
- HTTP 402 returned when no valid x402 payment token is provided, with EIP-3009 payment details in response extras
- Invalid or expired payment token causes 402 re-challenge
- Non-OpenX402 facilitators are rejected (only OpenX402 is supported)
- Malformed 'properties' query parameter may result in unexpected or empty response
- Network or server errors returning 5xx if the diagnostic endpoint is unavailable
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json",
"example": {
"sku": "wwwmatch149",
"note": "Example paid JSON shape. Not a live settle.",
"price": "$0.02",
"title": "Www Match 149"
}
}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"