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 / WORKSPACEPREVIEW
Equipment classGrant dateFrequency
  1. Find the device

    Explore collected applications and source evidence.

  2. Keep it in your favorites

    A useful list you can return to in your workspace.

  3. Bring it into your workflow

    Ask your AI assistant or call the REST API.

Try asking your assistant

“Look up this FCC ID and show me the source links.”

Illustrated workflow · results depend on collected coverage

Early access, with the evidence visible. Historical and detailed application coverage is incomplete. Missing records do not prove an FCC ID is invalid. Billing is sandbox-only; PDF hosting and document text search are not available yet.
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 →
Know what you are looking at

Evidence belongs beside the answer.

Source URLs, observation times, and explicit collection gaps help you decide what a record can—and cannot—tell you.

Understand coverage and limitations →
  • Original FCC exhibit locations preserved
  • Missing values stay missing
  • Collected details distinguished from pending work
  • No invented compliance or identity verdicts
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. Billing is sandbox-only during early access.

Your first integration starts here.

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