Equipment authorization, made usable

FCC data.
For your apps
and AI.

Search device authorizations, save your favorites, and give your AI tools the FCC metadata they need. One account. REST + MCP.

50 API units + 50 UI requests per month. No card needed.

FCC ID API / MCPEXAMPLE WORKFLOW
You

Find wireless devices with collected application details.

Your assistant calls search_fcc
What you can inspect

A searchable starting point

FCC IDApplicantEquipment classGrant status

Open a result to inspect its technical details and source links.

You

Look up [FCC ID] and show me its application history.

Your assistant calls lookup_fcc_id
What you can inspect

Context behind the identifier

ApplicationsMatch detailsGrant datesSource links

Inspect match details before treating a suggested FCC ID as an exact match.

You

Show the public exhibit links for [application ID].

Your assistant calls get_application
What you can inspect

A route back to the source

Exhibit titlesDocument typesFCC source URLsObservation times

Open the upstream FCC documents. Review the original filing alongside its metadata.

Three ways to work with FCC data through your AI assistant.
From one device to your whole workflow

Less digging. More useful context.

01 / Research

Search beyond a name

Filter by FCC ID, applicant, country, equipment class, dates, grant status, and overlapping frequencies. Read collected technical rows and grant notes.

Explore the workspace →
02 / Integrate

REST for apps. MCP for agents.

Use account-scoped keys, documented JSON responses, and predictable usage limits. Bring the same collected corpus into your agent workflow.

Choose your AI connection →
03 / Revisit

Your favorites. Always handy.

Save devices and searches, review observed metadata changes, and check lists of FCC IDs. Paid plans include bounded CSV exports with source links.

Start your favorite list →
Inside the response

Useful fields.
Traceable sources.

Know what you can build with before writing a line of code. Explore the response fields below; each group explains how to use the data.

01Start with an identityDevice & application
fcc_idapplicant_namegrantee_codeproduct_codepurposegrant_statusaction_date

Find an FCC ID, its applicant, and the applications we have collected. Filter by applicant, country, date, and grant status.

Explore the documentation →
02Understand the radioTechnical details
frequencies.lower_mhzfrequencies.upper_mhzprofiledetails

Search overlapping frequency ranges and inspect collected equipment details. Read frequency ranges alongside the application’s equipment classification.

Explore the documentation →
03Follow the documentsPublic exhibits
attachment_idtitleexhibit_typefile_typeurl

Read exhibit metadata and follow original FCC document locations. Find test reports, manuals and other public filings at their original source.

Explore the documentation →
04Follow the sourceSource details
source_idform_urlgrant_urlexhibits_url

Keep source links and observation dates beside the data, so your research stays connected to the original FCC records.

Explore the documentation →
Keep the useful ones.

Favorite devices, save repeat searches, and get optional daily email alerts for observed changes. Your workspace keeps research together.

Build your shortlist →
Built for the tools you already use

Your AI. Connected to FCC data.

Sign in with your email, approve read access, and start asking. REST and every connected assistant share one API allowance.

ChatGPT + FCC ID API

One connection.
A new way to research.

Add a custom MCP server and choose OAuth. Use the published client identity when offered; leave manually entered client credentials blank.

Full ChatGPT setup guide →
  1. 01
    Add a custom connector

    Use this server URL and select OAuth.

    https://api.fccidapi.com/mcp
  2. 02
    Sign in and approve

    Use your FCC ID API email code. Check the workspace and allow read access.

  3. 03
    Ask your first question

    “Search for wireless devices and show me the collected source links.”

Claude + FCC ID API

One connection.
A new way to research.

Add a custom web connector with OAuth sign-in. Leave the client ID and secret blank for automatic setup.

Full Claude setup guide →
  1. 01
    Add a custom connector

    Use this server URL and select OAuth.

    https://api.fccidapi.com/mcp
  2. 02
    Sign in and approve

    Use your FCC ID API email code. Check the workspace and allow read access.

  3. 03
    Ask your first question

    “Search for wireless devices and show me the collected source links.”

Grok + FCC ID API

One connection.
A new way to research.

Add a custom connector and select OAuth. Grok and the xAI console use the same FCC ID API server.

Full Grok setup guide →
  1. 01
    Add a custom connector

    Use this server URL and select OAuth.

    https://api.fccidapi.com/mcp
  2. 02
    Sign in and approve

    Use your FCC ID API email code. Check the workspace and allow read access.

  3. 03
    Ask your first question

    “Search for wireless devices and show me the collected source links.”

Muse + FCC ID API

One connection.
A new way to research.

Ask Muse to add this MCP server using OAuth. Automatic registration is supported. For manual setup, use client ID fccidapi-muse with no secret.

Full Muse setup guide →
  1. 01
    Add a custom connector

    Use this server URL and select OAuth.

    https://api.fccidapi.com/mcp
  2. 02
    Sign in and approve

    Use your FCC ID API email code. Check the workspace and allow read access.

  3. 03
    Ask your first question

    “Search for wireless devices and show me the collected source links.”

Custom connector availability depends on your AI provider’s plan and workspace policy. Prefer code? Connect Codex orClaude Code with an API key.

A small request. A useful starting point.

Prefer code? Start here.

One API key. JSON responses. The same metadata your assistant can access through MCP.

Follow the quickstart →

Using a coding assistant? Set up Codex orClaude Code with an API key.

Search collected applications
curl --get https://api.fccidapi.com/v1/search \
  --data-urlencode "q=wireless" \
  --data-urlencode "has_details=true" \
  --header "Authorization: Bearer $FCC_API_KEY"
Free to explore. Room to grow.

Start with 50. Build with millions.

Monthly API allowances shared by REST and MCP. Workspace searches are counted separately.

Most successful data requests use one API unit; bulk lookup uses one per submitted FCC ID. Rate limits apply.

Your first integration starts here.

Try the free workspace, then connect your assistant with OAuth or your application with an API key.