Back to Browse
x402-tools Method Probe
x402
x402-tools Method Probe is a paid API for AI agents from openclawproductions.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-02).
Probes a public URL using a specified HTTP method (GET, HEAD, or DELETE) to diagnose x402 payment-gated endpoints, returning structured diagnostics about the 402 response and EIP-3009 payment requirements.
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 object containing the SKU name, human-readable title, price (e.g. '$0.03'), and any EIP-3009 payment extras attached to the 402 response for the probed URL and method combination. On unpaid requests, returns HTTP 402 with payment metadata; on paid requests, returns the full diagnostic payload.
Example use cases
Debugging a failing x402 micropayment
“My agent is hitting a 402 on https://myservice.com/api/data with a GET request and the payment keeps failing — can you probe that URL with a GET to see exactly what EIP-3009 payment metadata and facilitator it's requiring?”
Auditing a new x402-gated endpoint
“I just deployed a new paid API at https://openclawproductions.com/api/v1/newfeature — probe it with a HEAD request to confirm it's correctly returning a 402 with the right x402 payment extras before I publish it.”
Comparing payment requirements across methods
“Can you probe https://partnerapi.io/resource using both GET and DELETE methods to see if the 402 payment requirements differ between them — I need to know the price and facilitator for each.”
Technical details
Endpoint
GEThttps://openclawproductions.com/api/v1/methodprobe?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to diagnose or audit x402-protocol-gated HTTP endpoints specifically — particularly to inspect EIP-3009 payment metadata, validate 402 response structure, or debug micropayment failures. It is purpose-built for the x402 ecosystem with OpenX402 as facilitator. Prefer it over generic HTTP probing tools when the target is a payment-gated API and you need structured payment metadata in the response.
Side effects
- HTTP 402 returned when payment header is missing or invalid — expected behavior for unpaid calls
- Invalid method enum (only GET, HEAD, DELETE accepted) causes request rejection
- Target URL is unreachable or returns non-402 response — probe may return unexpected diagnostic data
- OpenX402 facilitator unavailable — payment settlement fails
- Malformed URL in query params causes input validation error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"sku": "methodprobe",
"note": "Example paid JSON shape. Not a live settle.",
"price": "$0.03",
"title": "Method Probe"
}
}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"