# Us Customs Broker Registry List (`scrapebench/us-customs-broker-registry-list`) Actor

Every customs broker holding a CBP permit: filer code, firm name, city, state, phone and email. Export the whole list or check a broker by name or filer code.

- **URL**: https://apify.com/scrapebench/us-customs-broker-registry-list.md
- **Developed by:** [ScrapeBench](https://apify.com/scrapebench) (community)
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.005 / broker permit

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## US Customs Broker List & Permit Lookup Scraper (CBP)

### Pain points

- CBP publishes its permitted broker list as one CSV re-issued under a new dated file name about every month, linked only from an HTML page.
- The file has no search: checking one broker means opening the whole spreadsheet, and a firm with several office permits appears on several rows.
- Importers auditing the brokers they use before the new broker and importer-of-record requirements take effect have no easy way to check a roster of firm names against the list.

### What we solve

- Reads CBP's current file on every run, so you never chase the dated link.
- One uniform row per permit with a normalised phone and lower-cased email.
- Look up many broker names or filer codes in one run; a name matches if contained in the firm name, a filer code matches exactly.
- Keep only permits that list a phone ('Only brokers with a phone') or an e-mail ('Only brokers with an e-mail') to build a call or mail list in one run.
- Optional 'Include contact details' (off by default) looks up a phone for a broker CBP lists without one, by firm name and city; charged only on a row that gets one.
- A source CBP is not answering is a free row, never a silent empty result.

### Summary

Reads CBP's Permitted Customs Brokers Listing live and returns one row per broker permit: the three-character filer code, the firm name, city, state, phone and email where the broker filed them. Leave the queries empty for the whole list (2,500+ permits), filter by state or city, or give broker names or filer codes to check a roster.

### Who it's for

- Trade-compliance teams auditing the customs brokers their company uses
- Importers verifying a broker holds a current CBP permit and where it is based
- Logistics and freight sales teams building lists of customs brokers by state and city
- Trade-software and consulting vendors selling to customs brokers

### How to use

This actor does two jobs. Run it, then collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API).

**Get a list (export):** no names, just filters; returns the whole matching list.

```json
{
  "mode": "export",
  "states": [
    "TX"
  ],
  "maxResults": 500
}
```

**Check specific firms (lookup):** put company names or licence numbers in `mode`, `queries`; **Inputs** below says how each is matched.

```json
{
  "mode": "lookup",
  "queries": [
    "Livingston",
    "9H3"
  ],
  "maxResults": 20
}
```

See **Inputs** below for every available field.

### What you get

One row per record:

| Field | Description |
|---|---|
| `listing_id` | CBP filer code, three characters (not unique: a firm with several office permits has one row per office) |
| `name` | Permitted broker name as CBP lists it |
| `city` | City of the permit's office |
| `region` | Two-letter state |
| `phone` | Work phone as printed (present on about 61% of rows on 2026-11-16); with 'Include contact details' on, a phone found by firm name and city fills a row that had none |
| `phone_e164` | The same phone in +1XXXXXXXXXX form |
| `email` | Contact email, lower case (present on about 27% of rows on 2026-11-16) |
| `extras.phone_extension` | Phone extension where listed |
| `source_url` | CBP's listing page with the filer code and city |

Sample:

```json
{
  "listing_id": "9H3",
  "name": "T-LINK LOGISTICS INC",
  "phone": "909-860-5600",
  "phone_e164": "+19098605600",
  "email": "lsong@tlinklogistics.com",
  "city": "ONTARIO",
  "region": "CA",
  "country": "US",
  "category": "Permitted customs broker",
  "categories": [
    "Permitted customs broker"
  ],
  "source": "live",
  "source_url": "https://www.cbp.gov/about/contact/brokers-listing#filer-9H3-ontario",
  "extras": {}
}
```

### Inputs

| Field | Required | Type | Default | Description |
|---|---|---|---|---|
| `mode` | no | string | `"auto"` | export: no names, just filters; returns the whole matching list. lookup / verify: put company names (matched if contained in the company name) or licence numbers (exact) in 'queries'. auto picks the mode for you. |
| `query` | no | string | — | A business name (or listing number) to look up live. Kept alongside 'queries' for saved tasks. |
| `queries` | no | array | `[]` | A business name (or listing number) to look up live. Several values in one run; combined with 'query'. |
| `state` | no | string | — | Only listings in this state. Kept alongside 'states' for saved tasks. |
| `states` | no | array | `[]` | Only listings in this state. Several values in one run; combined with 'state'. |
| `city` | no | string | — | Only listings in this city. Kept alongside 'cities' for saved tasks. |
| `cities` | no | array | `[]` | Only listings in this city. Several values in one run; combined with 'city'. |
| `categories` | no | array | `[]` | Only rows from this broker list (one or more). Available: Permitted customs broker. |
| `includeContacts` | no | boolean | `false` | Off by default. Turn on to add a phone to each business row the list publishes none for, looked up by business name and city. Charged as a separate 'Contact details found' event only on a row that gets a phone; a row without one costs only the row price. |
| `hasPhone` | no | boolean | `false` | Keep only permits for which CBP's list gives a phone number (checked before any contact lookup). |
| `hasEmail` | no | boolean | `false` | Keep only permits for which CBP's list gives an e-mail address. |
| `maxResults` | no | integer | `500` | Per query in lookup mode; per run in export mode. |
| `proxyConfiguration` | no | object | `{"useApifyProxy": false}` | Used for every request to the source; off by default. |

### Pricing (Pay Per Event)

You pay per result (`dataset-item`) — **no charge for empty runs**. Example: **2590 broker permits** at *$0.005/result* ≈ **$12.95**.

$5 per 1,000 permits, no start fee. The whole list (2,500+ permits) is about $12. With 'Include contact details' on (off by default), a broker CBP lists without a phone that gets one is also charged a 'Contact details found' event ($0.002); every other row costs only the row. Notices are free.

### Use cases

- Broker roster check: is each broker we use on CBP's permitted list, and under which filer code (queries: the firm names).
- Look up a filer code from an entry document and see which firm it belongs to (queries: the code).
- Regional broker list: every permitted broker in Texas, or in Laredo (states / cities).
- Outreach list for customs-brokerage tooling: firm, phone and email for every permitted broker.
- Email-ready list: every permitted broker CBP lists an e-mail for ('Only brokers with an e-mail'), by state.

### Why this actor

- Reads the file CBP publishes today, not a copy from last quarter.
- Export and lookup in one actor, with many queries per run.
- A refused or changed source is a free row, never a failed run.

### Limitations & updates

Covers broker permits as CBP publishes them, with only the fields CBP lists (plus an optional looked-up phone); no licence numbers, bond status or compliance tier. The list is re-issued by CBP about monthly; each run reads the current file.

### FAQ

**Where does the data come from?**

U.S. Customs and Border Protection's Permitted Customs Brokers Listing (cbp.gov/about/contact/brokers-listing), the CSV the page links. Every run reads the current file.

**Does it include licence numbers, bond status or compliance ratings?**

No. CBP's public list has the filer code, firm name, city, state, phone and email only. Individual broker licence numbers, bonds and compliance tiers are not in any public CBP file this actor reads.

**Is a filer code unique?**

Not always. A firm with permits in several offices repeats its filer code with each office's city, so each permit is its own row.

**Why are some phones and emails empty?**

CBP's list leaves them blank where the broker filed none. By default the actor does not guess them. Turn on 'Include contact details' to look up a phone for a broker without one, by firm name and city; a phone is added only on a strict match, otherwise the row stays as CBP published it. E-mails are never looked up.

**Can I get only brokers with a phone or an e-mail?**

Yes: 'Only brokers with a phone' and 'Only brokers with an e-mail' keep only permits where CBP's own list has one. The phone filter is applied before any contact lookup.

**How do I look up a broker?**

Put firm names or filer codes in queries and set mode to lookup. A name matches if contained in the firm name; a filer code matches exactly.

**How am I charged?**

$0.005 per permit row returned, plus $0.002 'Contact details found' on a row that gets a phone when 'Include contact details' is on (off by default). Notices are free. Set Maximum results to cap spend.

### Guides & use cases

Written up on **[scrapebench.dev](https://scrapebench.dev)** — the bench that runs and verifies this actor against the live source every night:

- **How-to:** [How to run US Customs Broker List & Permit Lookup Scraper (CBP)](https://scrapebench.dev/guides/how-to-us-customs-broker-registry-list/)
- **Use case:** [Texas customs brokers list with phones and e-mails](https://scrapebench.dev/use-cases/texas-customs-brokers-list/)

More actors, coverage and nightly verification results: **[scrapebench.dev](https://scrapebench.dev)**

### Works with AI assistants (MCP)

Callable as an MCP tool, so Claude, Cursor, VS Code Copilot and other MCP clients can run it directly. Grab the config from the [MCP tab](https://apify.com/scrapebench/us-customs-broker-registry-list/api/mcp) on this page — Apify hosts the server and keeps that snippet current, and OAuth signs you in on first connect, so no API token goes in your config file.

Then just ask:

> "Check whether these customs brokers are on CBP's permitted list and give me their filer codes and states: Livingston, Expeditors, Kuehne."

Lookup mode, a name matches if contained in the firm name. Leave the queries empty for the whole list. Runs started this way bill exactly like any other run.

### Data & lawful use

This actor collects publicly available information that U.S. Customs and Border Protection (CBP) publishes for public
lookup — licence records, business listings and the contact details professionals list there.
Some of it identifies individuals (sole proprietors, licence holders, agents), so treat any
names, phone numbers and emails in your results as personal data.

When you run this actor, you decide what is collected and what it is used for, so you are the
controller of that data and we act only as your processor (Apify Standard Actor Contract).
You need a lawful basis for your use, must honour opt-out and deletion requests, and must
follow the marketing rules that apply to you (CAN-SPAM, TCPA, GDPR, CCPA and similar).
Don't use the output for unsolicited bulk messaging, for screening covered by the FCRA, or
for anything the source's own terms forbid.

Your results are stored in your own Apify account. We don't keep a copy of your results and
don't sell or share them.

### Disclaimer

This is an independent tool. It is not affiliated with, endorsed by or sponsored by
U.S. Customs and Border Protection (CBP). Names and marks are used only to describe the data source. Records are
provided as published by the source and may be out of date or incomplete. For anything
consequential (hiring, a permit, a legal decision), confirm the record with the issuing
agency. You are responsible for making sure your use complies with applicable law and the
source's terms.

### Need help?

Open an issue on this actor's **Issues** tab and we'll respond there. Bug reports, missing
fields and feature requests are all welcome. Guides and examples: [scrapebench.dev](https://scrapebench.dev).

If you are a person named in this data and want your record removed from our copy, email
apify-help@scrapebench.dev; the source agency remains the official record.

Your run may be used to improve our services. If something looks off, or you want this actor to fit your use better, please share your run data with us: [Apify Console → Settings → Security → Share run data with developers](https://console.apify.com/settings/security). It lets us see exactly what went wrong and keep improving the actor.

If this actor saved you time, a short review on its Store page helps other buyers find it.

# Actor input Schema

## `mode` (type: `string`):

export: no names, just filters; returns the whole matching list. lookup / verify: put company names (matched if contained in the company name) or licence numbers (exact) in 'queries'. auto picks the mode for you.

## `query` (type: `string`):

A business name (or listing number) to look up live. Kept alongside 'queries' for saved tasks.

## `queries` (type: `array`):

A business name (or listing number) to look up live. Several values in one run; combined with 'query'.

## `state` (type: `string`):

Only listings in this state. Kept alongside 'states' for saved tasks.

## `states` (type: `array`):

Only listings in this state. Several values in one run; combined with 'state'.

## `city` (type: `string`):

Only listings in this city. Kept alongside 'cities' for saved tasks.

## `cities` (type: `array`):

Only listings in this city. Several values in one run; combined with 'city'.

## `categories` (type: `array`):

Only rows from this broker list (one or more). Available: Permitted customs broker.

## `includeContacts` (type: `boolean`):

Off by default. Turn on to add a phone to each business row the list publishes none for, looked up by business name and city. Charged as a separate 'Contact details found' event only on a row that gets a phone; a row without one costs only the row price.

## `hasPhone` (type: `boolean`):

Keep only permits for which CBP's list gives a phone number (checked before any contact lookup).

## `hasEmail` (type: `boolean`):

Keep only permits for which CBP's list gives an e-mail address.

## `maxResults` (type: `integer`):

Per query in lookup mode; per run in export mode.

## `proxyConfiguration` (type: `object`):

Used for every request to the source; off by default.

## Actor input object example

```json
{
  "mode": "auto",
  "queries": [],
  "states": [],
  "cities": [],
  "categories": [],
  "includeContacts": false,
  "hasPhone": false,
  "hasEmail": false,
  "maxResults": 500,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per business listing; notices are free.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapebench/us-customs-broker-registry-list").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapebench/us-customs-broker-registry-list").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call scrapebench/us-customs-broker-registry-list --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapebench/us-customs-broker-registry-list"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3lhfedbD9AbpI7Vt2/builds/dFbEI1agkx0PQ7GeL/openapi.json
