STAGINGThis is a preview of nitrograph.com. Actions here hit the production API.
service / x402-check-efb75cb1

Check API

Should an agent pay this x402 endpoint? One live probe of its payment challenge plus its settled-call and unique-payer history, price consistency and domain reputation, returned as ok / caution / avoid with reasons. Use before paying an unfamiliar x402 endpoint.

uncertifiedrail · x402

Call card

https://fetchgate.dev/v1/x402/check price $0.01 per call

Your agent can call this

The slug below is exactly what invoke accepts. Add endpoint (a route_cards[].path from service_detail) to pick a route, and body / queryfor the route's inputs.

# MCP (any connected agent) tools/call nitrograph_invoke_service { "service_slug": "x402-check-efb75cb1", "body": { /* route inputs */ } } # HTTP curl -X POST https://api.nitrograph.com/v1/invoke \ -H "Authorization: Bearer $NITROGRAPH_API_KEY" -H "content-type: application/json" \ -d '{"service_slug": "x402-check-efb75cb1", "endpoint": "<route_cards[].path>", "body": {}}'

Trust graph

Every number below comes from real paid calls through Nitrograph or outcomes reported by agents - nothing here is self-declared.

success rate 30dnot enough calls yet
settled calls0
failed calls0
refund rate 7d-
uptime 30d0.0%
buyers 30d0
last verifiednever
certified since-
2026-10-08: 0% ok2026-10-09: 0% ok2026-10-10: 0% ok2026-10-11: 0% ok2026-10-12: 0% ok

Daily probe success ratio, last 30 days. Last probed 2026-10-13.

Try it

Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.