Back to Browse
Agent Paywire URL Payment Protocol Check
x402
Agent Paywire URL Payment Protocol Check is a paid API for AI agents from api.agentpaywire.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-29).
Checks whether a given public URL supports AI agent payment protocols (x402/L402) and returns a detailed compliance report
Price / call$0.05
Success—
StatusUnknown
How this service works
Check whether a public URL exposes L402, x402, or MPP discovery. Send url as a query parameter. POST JSON {"url":"https://..."} is the same check. Two free reports per client per 24 hours, then 0.05 USDC. A request without url is the payment challenge and does not use a free report.
Output
Returns a JSON object with the queried URL, a boolean 'paid' flag indicating payment protocol support, and a 'report' object containing the protocol name (e.g. 'l402+x402'), a summary of pass/fail test counts, and detailed compliance test results.
Example use cases
Vetting a new paid API for agent use
“Before I wire up this weather API at https://api.weatherpro.com/v1/forecast to my agent pipeline, can you check if it actually supports x402 or L402 so the agent can pay for it on its own?”
Debugging an agent payment failure
“My agent is failing to pay for https://api.dataservice.io/v1/prices — can you run a compliance check on that URL and tell me which payment protocol tests are passing or failing?”
Auditing a directory of agentic APIs
“I'm building a list of APIs my agents can use autonomously. Can you check if https://api.newservice.com/v1/data is x402-compliant and show me the full report?”
Technical details
Endpoint
GEThttps://api.agentpaywire.com/v1/check?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to programmatically verify whether a specific public URL supports AI agent-native payment protocols (x402 or L402) before integrating it into an agentic workflow. It is ideal for pre-flight checks in agent pipelines, auditing directories of paid APIs, or debugging payment negotiation failures. Prefer this over manual inspection or generic HTTP probing tools when you want structured, protocol-aware compliance reports specific to machine-to-machine payment standards.
Side effects
- URL is not publicly reachable — network error or timeout returned
- URL does not implement any payment protocol — paid: false with fail counts in summary
- Invalid or malformed URL provided — validation error
- Endpoint requires authentication before protocol headers are visible
- Rate limiting or upstream errors from the target server interfere with probing
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"url": "https://api.example.com/v1/weather",
"paid": true,
"report": {
"ok": true,
"url": "https://api.example.com/v1/weather",
"summary": {
"fail": 0,
"pass": 4
},
"protocol": "l402+x402"
}
}
}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"