service / x402-zap-radar-1633a358
Zap Radar API
Collects kind 9735 zap receipts addressed to one public key over up to twelve relays, merges them by event id and reports who sent how much over the requested window. Every amount comes from decoding the BOLT-11 invoice carried in the receipt, not from the amount tag of the zap request, because the two can disagree and only the invoice was payable.
uncertifiedrail · x402
Call card
https://nostr.halowerk.com/zap-radar
price $0.004 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-zap-radar-1633a358", "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-zap-radar-1633a358", "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 30d100.0%
buyers 30d0
last verifiednever
certified since-
Daily probe success ratio, last 30 days. Last probed 2026-11-05.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.