service / x402-locus-traffic-crash-context-78201ac1
Aggregate Traffic Crash Context Near An Address API
Aggregate traffic-crash context near an address. Perfect for: 'traffic crashes near this property', 'pedestrian or bicycle crash counts nearby', 'fatal crash context around an address'. Returns small-cell-suppressed official aggregates with explicit severity classes: local sources where wired plus nationwide FARS fatal-only fallback. Not route exposure, a forecast, score, or place verdict. Charge-free unless at least one count survives small-cell suppression.
uncertifiedrail · x402
Call card
https://api.locus.report/api/locus-traffic-crash-context
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-locus-traffic-crash-context-78201ac1", "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-locus-traffic-crash-context-78201ac1", "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 30d53.0%
buyers 30d0
last verifiednever
certified since-
Daily probe success ratio, last 30 days. Last probed 2026-10-04.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.