Back to Browse
x402-tools Min Ping Share Diagnostic
x402
x402-tools Min Ping Share 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-10).
Returns a paid diagnostic JSON payload (minpingshare SKU) via the x402 micropayment protocol, returning HTTP 402 with EIP-3009 payment details if unpaid.
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 ('minpingshare'), a human-readable diagnostic note, the price ('$0.02'), and a title ('Min Ping Share'). If the $0.02 USDC micropayment via x402 has not been settled, the server returns HTTP 402 with EIP-3009 payment challenge extras instead.
Example use cases
Integration smoke test for x402 agent
“Can you hit the minpingshare x402 endpoint and confirm that after paying $0.02 USDC the server returns a valid paid JSON payload? I want to make sure my agent's x402 payment loop is working correctly.”
Debugging HTTP 402 EIP-3009 challenge
“I'm getting a 402 response from the OpenX402 facilitator and I'm not sure my EIP-3009 extras are being parsed right — can you probe the minpingshare diagnostic endpoint and show me the raw 402 challenge details before payment?”
Verifying OpenX402 facilitator connectivity
“Check whether the OpenX402 facilitator is reachable and responding correctly by calling the minpingshare diagnostic SKU — just confirm it's returning the expected title and price fields in the paid response.”
Technical details
Endpoint
GEThttps://openclawproductions.com/api/v1/minpingshare?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need a live, low-cost ($0.02 USDC) end-to-end test of the x402 micropayment protocol with the OpenX402 facilitator — particularly for validating EIP-3009 payment challenge/response flows, checking that an AI agent can automatically detect and settle HTTP 402 responses, or confirming the shape of a paid x402 JSON payload before integrating a production SKU.
Side effects
- HTTP 402 returned when no valid x402 payment header is present, with EIP-3009 payment challenge in response extras
- Payment rejected if facilitator is not OpenX402
- Malformed or missing properties parameter may yield unexpected behavior
- Network timeout if openclawproductions.com is unreachable
- Payment settlement failure if USDC balance is insufficient
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json",
"example": {
"sku": "minpingshare",
"note": "Example paid JSON shape. Not a live settle.",
"price": "$0.02",
"title": "Min Ping Share"
}
}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"