canonical: https://jentic.com/apis/runalphaloops.com/runalphaloops

# Runalphaloops AlphaLoops FMCSA Carrier Data API

The AlphaLoops FMCSA Carrier Data API returns fleet intelligence on FMCSA-registered motor carriers, looked up by DOT number, MC or MX docket number, or company name. For a carrier it serves the profile, operating authority history, insurance filings, truck and trailer fleet, inspections and violations, crashes, news mentions, a change-event timeline, and aggregated risk signals. It also benchmarks a carrier's safety record against a peer group, finds decision-maker contacts at the company, decodes VINs in batches of up to 100, and lists authority-for-sale records.

## For AI agents

Look up FMCSA motor carriers by DOT or MC number or name, then read their authority, insurance, fleet, inspections, crashes, risk signals, safety benchmark, and company contacts.

## Scope

Does not book loads, dispatch drivers, or file FMCSA registrations. Use for reading motor carrier profiles, safety records, fleet data, and contacts only.

## Capabilities

- Look up a carrier profile by DOT number or MC/MX docket number, with field projection through the fields parameter
- Match a company to a carrier by company_name, domain, state, or city, or run filtered queries with include and exclude conditions
- Read a carrier's operating authority history, insurance filings, and change-event timeline
- Pull inspection history with per-inspection violations, and crash history filtered by severity such as FATAL or INJURY
- List a carrier's trucks and trailers and look up up to 100 VINs per request with their inspection history
- Score a carrier with aggregated risk signals and a safety benchmark against a chosen peer_group
- Find people at a carrier by job_title and enrich a contact with verified emails and phone numbers

## Use cases

### AI agent vetting a carrier before tendering a load

A freight broker's AI assistant needs to vet an unfamiliar carrier quickly before a load is tendered. Through Jentic the agent searches for 'look up a carrier by DOT number', loads the getCarrierByDot operation with its input schema, and calls it with the bearer key injected at execution time. It then reads the carrier's authority history, insurance filings, and risk signals and returns a short go or hold recommendation with the reasons.

Example prompt: Call GET `/v1/carriers/{dot_number}` for DOT 1234567, then GET `/v1/carriers/{dot_number}/authority`, GET `/v1/carriers/{dot_number}/insurance`, and GET `/v1/carriers/{dot_number}/risk-signals`, and summarise any red flags

### Carrier prospecting with filtered search

A sales team selling to trucking companies wants carriers that match a profile rather than a known name. POST `/v1/carriers/query` accepts include and exclude conditions, sorting, field projection, and paging, so a team can filter by state, fleet size, cargo type, or authority status. Matching carriers can then be passed to the contacts search to find decision-makers by job title.

Example prompt: Send POST `/v1/carriers/query` with include conditions for state TX and a minimum power unit count, then call GET `/v1/contacts/search` with each dot_number and job_title set to safety director

### Safety and compliance monitoring

An insurer or shipper monitoring its carrier base tracks inspections, violations, and crashes over time. The API returns inspection history with a violations lookup per inspection_id, crash history filterable by start_date, end_date, and a severity enum including FATAL, INJURY, TOW, and PROPERTY_DAMAGE, and a safety benchmark that compares the carrier against a peer group. A change-event timeline surfaces authority and profile changes between reviews.

Example prompt: Call GET `/v1/carriers/{dot_number}/crashes` with severity FATAL and a start_date one year back, then GET `/v1/carriers/{dot_number}/safety-benchmark` with a peer_group from GET `/v1/peer-groups`

### Fleet VIN verification

A lender or equipment buyer verifying a carrier's trucks checks the VINs it reports. POST `/v1/vins` looks up as many as 100 VINs in one request, preserving input order and marking misses with found set to false. GET `/v1/inspections/vin/{vin}` returns the inspection history for a single vehicle, and the trucks and trailers routes list a carrier's own fleet for comparison.

Example prompt: Send POST `/v1/vins` with the carrier's reported VINs, then call GET `/v1/inspections/vin/{vin}` for any VIN that was found, and flag VINs missing from GET `/v1/carriers/{dot_number}/trucks`

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/carriers/{dot_number}` | Look up a carrier by DOT number |
| GET | `/v1/carriers/mc/{mc_number}` | Look up a carrier by MC docket number |
| GET | `/v1/carriers/search` | Match a company to a carrier by name |
| POST | `/v1/carriers/query` | Run a filtered carrier search |
| GET | `/v1/carriers/{dot_number}/insurance` | Get insurance filings |
| GET | `/v1/carriers/{dot_number}/risk-signals` | Get aggregated risk signals |
| GET | `/v1/carriers/{dot_number}/crashes` | Get crash history |
| GET | `/v1/contacts/search` | Find people at a carrier |

## Key resources

- **Carriers** — FMCSA-registered carriers keyed by DOT number or MC docket, with profile, authority, insurance, timeline, connections, similar carriers, and an AI-generated overview
- **Safety records** — Inspections, per-inspection violations, crashes, risk signals, and peer-group safety benchmarks
- **Fleet and VINs** — Truck and trailer fleets, equipment listed for sale, VIN lookups, and VIN inspection history
- **Contacts** — People at carrier companies, searchable by job title and enrichable with verified emails and phone numbers
- **Authority-for-sale and custom data** — MC authority-for-sale listings and account-specific custom-data records per DOT number

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 62 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 80 / 100
- **View full report:** https://jentic.com/apis/runalphaloops.com/runalphaloops/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring AlphaLoops by hand means attaching the Enterprise bearer key to each request, resolving DOT versus MC identifiers, and paging through inspections, crashes, and timelines with their own filters. Through Jentic you install once, import AlphaLoops from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** AlphaLoops puts the DOT number in the URL path (`/v1/carriers/{dot_number}/...`), so a rule can pin your agent to the carriers you name and the reads you pick. You choose the operations it may call, so credit-consuming ones like contact enrichment are not included unless you add them.
- **Credential handling:** Your AlphaLoops API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up a carrier by DOT number' or 'get crash history', and Jentic returns the matching AlphaLoops operation with its input schema, including filters like severity and start_date, so the agent calls it directly.

## Related APIs

- **CarrierScrub** — Carrier vetting verdicts with FMCSA reason codes by DOT or MC number
- **NHTSA Vehicle API (vPIC)** — Free public VIN decoding and vehicle make and model data
- **Samsara** — Fleet telematics for a carrier's own vehicles, drivers, and locations
- **Apollo** — General B2B contact and company data across industries

## FAQ

### What authentication does the AlphaLoops FMCSA Carrier Data API use?

Per its OpenAPI spec, the AlphaLoops API uses HTTP bearer authentication: send your AlphaLoops API key in the Authorization header as Bearer YOUR_API_KEY on every operation. The spec states that API access is available on the Enterprise plan through AlphaLoops sales. Through Jentic the key is held by your own instance and attached at call time.

### Can I look up a carrier by MC number with the AlphaLoops API?

Yes. GET `/v1/carriers/mc/{mc_number}` returns the carrier for an MC or MX docket number, and GET `/v1/carriers/mc/{mc_number}/insurance` returns its insurance filings directly. For everything else, take the DOT number from the profile and use the `/v1/carriers/{dot_number}` routes.

### Does contact enrichment cost credits?

Yes. Per the spec, GET `/v1/contacts/{contact_id}/enrich` consumes one enrichment credit per new lookup, cached results are free, and the API returns HTTP 402 when credits are exhausted. Search with GET `/v1/contacts/search` first and enrich only the contacts you need.

### What are the rate limits for the AlphaLoops FMCSA Carrier Data API?

The OpenAPI spec does not specify request rate limits, though it caps batch sizes at 100 VINs per POST `/v1/vins` call and 500 DOT numbers per custom-data lookup. Check with AlphaLoops at https://runalphaloops.com/contact for the limits on your Enterprise plan.

### Is there an AlphaLoops MCP server?

You do not need an MCP server to give your agent the AlphaLoops API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the carrier, safety, and contact operations it needs on demand without extra tool definitions in its context.

### How do I check a carrier's risk through Jentic?

Search Jentic for 'get carrier risk signals', load the GET `/v1/carriers/{dot_number}/risk-signals` operation, and execute it with the DOT number. Set include_equipment when you want equipment signals in the result. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the AlphaLoops API?

Yes. Write a rule that allows only the carrier profile, authority, and insurance reads, so the agent can vet carriers but cannot search contacts or run credit-consuming contact enrichment. Because the DOT number sits in the path, you can also pin a rule to the carriers you already work with, and every call is logged.
