service / x402-report-a33b67a0
Agent Weather
Use when you need pre-flight readings of liveness, valid-402 status and price/payTo drift for known XRPL x402 endpoints. Health of known x402 endpoints on XRPL and of the t54 facilitator: per-endpoint liveness and valid-402 check from one unpaid GET every 20 min (merchants' own /.well-known/x402 catalogs plus endpoints we discovered), price, asset, network and payTo drift versus the previous check, catalog reachability, and facilitator health from /supported reachability and our own ledger scan (success rate, fee spikes, tagged volume). JSON with sources and data gaps. Example (illustrative): GET /v1/health/report → {endpoints:[{url, status, valid_402, ms}], drift[], facilitator}. Price: 0.01 RLUSD on XRPL mainnet (xrpl:0; RLUSD issuer rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De) or 0.01 USDC on Base. Terms: https://api.agentweather.io/v1/terms
uncertifiedrail · x402
Call card
https://api.agentweather.io/v1/health/report
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-report-a33b67a0", "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-report-a33b67a0", "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 30d-
buyers 30d0
last verifiednever
certified since-
Daily probe success ratio, last 30 days. Last probed 2026-10-17.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.