fleetfax DEVELOPERS
Build on the carrier record
fleetfax reads the public FMCSA record for every US motor carrier and freight broker and surfaces it as one plain carrier profile: authority, insurance on file, safety data, and descriptive findings. Soon you will be able to reach that same profile from an AI assistant or your own code. fleetfax surfaces the facts; you make the call.
The connectors and the REST alias are not open yet. This page documents the addresses and the exact shape they answer with, so an integration can be written against them ahead of time. They start answering when the fleetfax developer program opens.
Assistants
Connect an assistant
The fleetfax connector speaks the Model Context Protocol (MCP), an open standard for connecting assistants to tools. Both connectors open soon. Their addresses and what each one returns are below, so a setup is ready to run on the day they answer.
Free Opens soon
Look up any carrier by USDOT, MC, or name, and read the public snapshot fleetfax surfaces. No account needed. A daily lookup limit applies, and it resets each day.
https://api.fleetfax.com/mcpPro Opens soon
Everything in free, plus a carrier's full history, your watchlist and alerts, and batch checks of up to ten carriers at once. Opens soon, and will need a fleetfax Pro plan.
Opens soonNew to connectors? Each setup guide walks the steps for one assistant, ready to follow on the day the connectors open.
API
Call it from code
A REST alias returns the same carrier profile as JSON, described by an OpenAPI 3.1 spec. Look a carrier up by USDOT or MC number, or search by name. Every response links the live fleetfax report and carries an attribution string. The alias opens alongside the connectors; what follows is the shape it answers with.
GET /ai/carrier/{query} and GET /ai/search?name=. It does not answer yet; when the API opens you will be able to drop it into a ChatGPT custom action or an OpenAPI client.
Carrier Risk Profile schema/schema/carrier-risk-profile-v1.json
A versioned JSON Schema (draft 2020-12) for the carrier profile: the identity block, authority and insurance restatements, the findings array with stable reason codes, and the descriptive verdict state. No book / do-not-book field and no composite score, by design.
curl https://api.fleetfax.com/ai/carrier/9999999 # by MC number curl "https://api.fleetfax.com/ai/carrier/MC9999999" # search by name curl "https://api.fleetfax.com/ai/search?name=example%20carrier"
Numbers above are placeholders. Swap in a real USDOT or MC number. These calls do not answer yet: they are here so an integration can be written against the shape before the API opens.
The contract
The standard
The carrier profile fleetfax returns is descriptive by design. It restates the public federal record, an identity block, operating authority, insurance on file, safety data, and discrete findings, and summarizes the findings in one descriptive line. It never rolls that into a book or don't-book instruction and never into a safety, risk, or quality score. That judgment stays with you.
The response shape is published, not proprietary. The OpenAPI spec and the Carrier Risk Profile schema describe every field and its source, so an integration can read a fleetfax profile, or speak the same shape, without guessing. Field names, the stable finding reason codes, and the verdict states are a contract; the schema version moves when they do.
Terms
Terms and limits
The data is public FMCSA record fleetfax surfaces: observed is not booked, absence is not proof, and self-reported is not verified. The free connector and the REST alias will share a daily lookup limit; higher-volume access is rolling out on fleetfax Pro. Use is governed by the fleetfax terms and privacy policy.