# FCC ID Equipment Authorization Lookup (`bakos_bence/fcc-id-lookup`) Actor

Look up FCC equipment authorization grants by FCC ID or grantee-code prefix via the official OET Lab Services API. Returns grantee org, grant date, purpose, and address fields. Unofficial; not affiliated with the U.S. Federal Communications Commission.

- **URL**: https://apify.com/bakos\_bence/fcc-id-lookup.md
- **Developed by:** [Bakos Bence](https://apify.com/bakos_bence) (community)
- **Categories:** Developer tools, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.25 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does FCC ID Equipment Authorization Lookup do?

**Look up FCC equipment authorization grants** by **FCC ID or grantee-code prefix** via the official **OET Lab Services** JSON API (`apps.fcc.gov/OETLabServices/getFCCIDList`). Each row includes **grantee organization**, **grant date**, **application purpose**, and **org address fields** (city, state, country, zip). No login. Export **JSON or CSV** via Apify API, schedule, or MCP.

**Unofficial.** This Actor is **not affiliated with, endorsed by, or maintained by** the U.S. Federal Communications Commission. It reads **public** OET endpoints only.

**Dashboards:** connect **Power BI**, **Tableau**, **Looker Studio**, or **Qlik** to the dataset API — see *Export to Power BI, Tableau, Looker Studio & Qlik* near the end. **AI agents:** paste this Actor’s Store page URL into an Apify-capable agent (MCP / Claude / Cursor with Apify), create an Apify account and API token once, and the agent can run the Actor and wire up the output.

#### Why use this FCC ID lookup?

- 📡 Official OET Lab Services JSON — grantee org facts, not scraped HTML
- 🔍 Prefix search (e.g. `BCG` → Apple Inc. grants)
- 🏢 Org address fields preserved for compliance / supply-chain checks
- 🛡️ curl\_cffi TLS — works when plain HTTP clients get Access Denied

#### How to look up FCC IDs

1. Open this Actor in [Apify Console](https://console.apify.com/).
2. Click **Start** on the prefilled `BCG` prefix (`maxItems` 5), or enter your own FCC IDs.
3. Leave `proxyType` on `none` unless `apps.fcc.gov` blocks your IP.
4. Export the dataset or pull via API.

```json
{
  "fccIds": ["BCG"],
  "maxItems": 5,
  "proxyType": "none"
}
```

#### How much does it cost?

**Pay per event (PPE):** Actor start + each **result** row. See the Pricing tab on this Actor’s Store page.

#### Input

| Field | Description |
|-------|-------------|
| `fccIds` | FCC ID or grantee-code prefix values |
| `maxItems` | Cap on grant rows |
| `proxyType` | Optional proxy |

#### Sample output

```json
{
  "fccid": "BCG-2310",
  "grantee": "Apple Inc.",
  "grantDate": "09/09/2009",
  "applicationPurpose": "Original Equipment",
  "city": "Cupertino",
  "state": "CA",
  "country": "United States",
  "address": "One Apple Park Way N/A",
  "zipCode": "95014",
  "sourceUrl": "https://apps.fcc.gov/OETLabServices/getFCCIDList?fccId=BCG",
  "scrapedAt": "2026-09-09T11:00:00+00:00"
}
```

#### FAQ

##### Is this an official FCC product?

No. It is unofficial and not affiliated with the FCC.

##### Do I need an FCC account?

No — only the public OET Lab Services endpoint.

##### Can AI agents call this?

Yes — Actor ID `bakos_bence/fcc-id-lookup` via Apify API or [MCP](https://mcp.apify.com).

##### Something broke?

Open the **Issues** tab on this Actor’s page.

#### Related Actors

| Actor | Use together when… |
|-------|-------------------|
| [Domain Typosquat Scanner](https://apify.com/bakos_bence/domain-typosquat-scanner) | You need brand/domain risk checks alongside device compliance |
| [Public Document Finder](https://apify.com/bakos_bence/public-document-finder) | You need broader public-records routing alongside FCC grant lookup |

Profile: [bakos\_bence on Apify](https://apify.com/bakos_bence).

#### For AI agents & LLM apps

Paste this Actor’s **Apify Store URL** into an agent that can use Apify (MCP, Claude, Cursor, etc.). With an Apify account and API token, the agent can set input, run the Actor, and fetch the dataset.

#### Export to Power BI, Tableau, Looker Studio & Qlik

1. Run the Actor (or open a finished run).
2. Open the **Dataset** → **API** / **Export**.
3. Copy the dataset items URL (JSON or CSV).
4. In your BI tool, add a **web / API** data source with that URL (and your Apify token as a header or query param if required).
5. Refresh on a schedule that matches your device-compliance monitoring cadence.

Grant facts are public FCC OET records — always verify critical certifications against primary FCC filings.

# Actor input Schema

## `fccIds` (type: `array`):

FCC ID or grantee-code prefix values to look up (e.g. BCG for Apple Inc.). Case-insensitive.

## `maxItems` (type: `integer`):

Cap how many grant rows to push. Leave at 5 for a cheap first run.

## `proxyType` (type: `string`):

Leave on none for most runs. Enable Apify Proxy if apps.fcc.gov blocks your datacenter IP.

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

Used only when Proxy is Apify Proxy.

## Actor input object example

```json
{
  "fccIds": [
    "BCG"
  ],
  "maxItems": 5,
  "proxyType": "none",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

Default dataset items.

# 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 = {
    "fccIds": [
        "BCG"
    ],
    "maxItems": 5,
    "proxyType": "none"
};

// Run the Actor and wait for it to finish
const run = await client.actor("bakos_bence/fcc-id-lookup").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 = {
    "fccIds": ["BCG"],
    "maxItems": 5,
    "proxyType": "none",
}

# Run the Actor and wait for it to finish
run = client.actor("bakos_bence/fcc-id-lookup").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 '{
  "fccIds": [
    "BCG"
  ],
  "maxItems": 5,
  "proxyType": "none"
}' |
apify call bakos_bence/fcc-id-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bakos_bence/fcc-id-lookup"
        }
    }
}

```

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/BMZwIG6zJpIGTR9Xl/builds/vtAb5eErv7WLec2JV/openapi.json