service / x402-check-address-consistency-bc80c044
check_address_consistency
Use this as a lighter-weight fraud signal than check_carrier_identity: how many distinct business addresses and phone numbers a carrier reports across FMCSA's independent records of it (census, licensing and insurance, crash reports). Several different addresses on one carrier is a common re-registration tell. Billed whenever the USDOT number resolves.
uncertifiedrail · x402
Call card
https://fmcsa-mcp-843680657471.us-central1.run.app/x402/check_address_consistency
price $10000.00 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-address-consistency-bc80c044", "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-address-consistency-bc80c044", "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-03.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.