Look up motor carrier
Motor Carrier Lookup returns the FMCSA record of a trucking or bus company from its USDOT number or its MC, MX or FF docket number. It covers USDOT status, entity and operation type, addresses, dockets, fleet and driver counts, MCS-150 date, safety rating, out-of-service orders, operating authority status and insurance on file. Paid plans add contact details, cargo classes, equipment, mileage, crash rate, insurance policies, authority history and pass/fail compliance checks with your own thresholds. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.
A real response from the Motor Carrier Lookup Skill — exactly what your agent gets back when it makes the call.
{
"dot": "80806"
}Enable Motor Carrier Lookup and your app or agent can look up motor carrier on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.
Over MCP, Motor Carrier Lookup appears to your model as the motorcarrierlookup tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.
Prefer to call it directly? Any language that can send a GET can hit Motor Carrier Lookup to look up motor carrier inline in your own server-side code.
Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.
It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.
motorcarrierlookupCall it from your server with one request and your key. Node, Python, Go — anything that can send a GET.
GET /v1/motorcarrierlookupHow to connect it over MCP or REST.
Same data, same VerveKit account, same credit balance — one key works on all of them.
The same key runs from your first prototype to millions of calls — on APIVerve's rails, 99.9% uptime.
See pricing
