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

# CarrierScrub API

The CarrierScrub API vets motor carriers for freight brokerages using FMCSA records. A single lookup takes a carrier's USDOT or MC number and returns a GO, CAUTION, or STOP verdict with dated reason codes, and a batch call checks a list of carriers from a CSV or XLSX file. Two open endpoints report how many carriers' FMCSA authority, insurance, and contact records changed over a day or week and give the full dated history of a carrier's operating authority. Every result names the FMCSA record it used and that record's date, and each reason states a published fact rather than a conclusion about the company.

## For AI agents

Check a motor carrier by USDOT or MC number for a GO, CAUTION, or STOP verdict with dated FMCSA reason codes, in single or batch form. Read authority history and weekly FMCSA record-change activity without a key.

## Scope

Does not book loads, track shipments, or set carrier rates. Use for FMCSA-based carrier vetting, authority history, and record-change activity only.

## Capabilities

- Check one carrier by USDOT or MC number for a GO, CAUTION, or STOP verdict
- Return dated reason codes that each cite a published FMCSA fact
- Check a list of carriers in batch from a CSV or XLSX file
- Read every dated grant, suspension, revocation, and reinstatement of a carrier's operating authority
- Report how many carriers' FMCSA authority, insurance, and contact records changed in a day or week

## Use cases

### Agent-Run Carrier Vetting

Before a brokerage agent tenders a load, it checks the carrier by USDOT or MC number through Jentic and reads the GO, CAUTION, or STOP verdict with its dated FMCSA reason codes. Each reason names the FMCSA record it used and that record's date, so the agent acts on published facts, not inferences. A rule can keep the agent on the carrier-check operations and nothing else.

Example prompt: Check a carrier by its MC number and block the load tender if the verdict is STOP, logging the reason codes.

### Bulk Carrier Screening

An operations team screens a whole carrier list at once by uploading a CSV or XLSX file to the batch endpoint, getting a verdict and dated reasons for each row. CarrierScrub dates every result and names the FMCSA record it drew from, so a bulk run is reproducible. Teams use this to re-screen their approved carrier base on a schedule.

Example prompt: Upload a CSV of 500 carriers to the batch endpoint and flag every row returning CAUTION or STOP.

### Authority and Activity Monitoring

A compliance workflow reads a carrier's full authority history, every dated grant, suspension, revocation, and reinstatement, and tracks how many carriers' FMCSA authority, insurance, and contact records changed over a day or week. Both of these endpoints are open and need no key, so monitoring runs without credentials. This surfaces carriers whose authority recently lapsed.

Example prompt: Pull the authority history for a carrier and alert if a revocation is dated in the last 30 days.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/lookup` | Check one carrier by USDOT or MC number |
| POST | `/v1/batch` | Check a list of carriers from a CSV or XLSX file |
| GET | `/v1/authority-history` | Read a carrier's dated operating-authority history |
| GET | `/v1/fmcsa-activity` | Count carriers whose FMCSA records changed in a day or week |

## Key resources

- **Carrier lookup** — Check one carrier by USDOT or MC number for a GO, CAUTION, or STOP verdict with dated reason codes
- **Batch check** — Check a list of carriers from an uploaded CSV or XLSX file
- **Authority history** — Every dated grant, suspension, revocation, and reinstatement of a carrier's operating authority
- **FMCSA activity** — How many carriers' authority, insurance, and contact records changed in a day or week

## 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:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 38 / 100
- **View full report:** https://jentic.com/apis/carrierscrub.com/carrierscrub/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 the CarrierScrub API by hand means creating an Agency-plan key, sending it as a bearer token, and remembering the FMCSA activity and authority-history endpoints are open while the lookup and batch calls are not. Through Jentic you install once, import CarrierScrub from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** CarrierScrub exposes four read endpoints and no write operations, so a rule bounds your agent to the single carrier lookup, the batch check, the authority history, or the FMCSA activity feed. You choose which of those it may call, and nothing it can reach changes a record.
- **Credential handling:** Your CarrierScrub 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 'check a carrier by USDOT number', and Jentic returns the matching CarrierScrub operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **OpenCorporates** — Official company-registry records for legal-entity due diligence.
- **Clearbit** — Company firmographic enrichment from a domain or email.
- **FullContact** — Contact and company enrichment from identifiers.

## FAQ

### What authentication does the CarrierScrub API use?

The CarrierScrub API authenticates with a bearer token in the Authorization header, per its OpenAPI spec, using keys that start with cs_live_. An owner or admin of an Agency-plan brokerage creates the key, and a key unused for 60 days stops working. The FMCSA activity and authority-history endpoints are open and need no key. Through Jentic the token is stored encrypted by your own Jentic One instance and injected only at call time.

### Can I check a carrier's FMCSA status with the CarrierScrub API?

Yes. A single lookup takes a USDOT or MC number and returns a GO, CAUTION, or STOP verdict with dated reason codes, and a batch call checks a list from a CSV or XLSX file. You can also read a carrier's full operating-authority history and weekly FMCSA record-change counts.

### What are the rate limits for the CarrierScrub API?

The OpenAPI spec does not specify rate limits for the CarrierScrub API. Check the vendor's documentation at https://carrierscrub.com/auth.md for current limits and plan details.

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

Yes. Write a rule that allows only the single carrier lookup, or add the batch check and the open history and activity reads, so the agent can vet carriers and nothing more. There are no write operations in this API, and every call it makes is logged.

### Is there a CarrierScrub MCP server?

You don't need an MCP server to give your agent the CarrierScrub API. Jentic connects it directly from the API Directory: import it, store your Agency-plan key once, and your agent calls the carrier lookup and history operations. You skip loading another server's tool definitions into the agent's context.

### How do I vet a carrier through Jentic?

Add the CarrierScrub API from the Jentic API Directory and store your Agency-plan key once. Your agent then searches by intent such as 'check a carrier by MC number' and Jentic returns the matching operation with its input schema, so it can read the verdict and reason codes. To run it on your own infrastructure, install Jentic One from its GitHub repo.