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 →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.
Explore collected applications and source evidence.
A useful list you can return to in your workspace.
Ask your AI assistant or call the REST API.
“Look up this FCC ID and show me the source links.”
Illustrated workflow · results depend on collected coverage
Filter by FCC ID, applicant, country, equipment class, dates, grant status, and overlapping frequencies. Read collected technical rows and grant notes.
Explore the workspace →Use account-scoped keys, documented JSON responses, and predictable usage limits. Bring the same collected corpus into your agent workflow.
Choose your AI connection →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 →Source URLs, observation times, and explicit collection gaps help you decide what a record can—and cannot—tell you.
Understand coverage and limitations →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.
curl --get https://api.fccidapi.com/v1/search \ --data-urlencode "q=wireless" \ --data-urlencode "has_details=true" \ --header "Authorization: Bearer $FCC_API_KEY"
Monthly API allowances shared by REST and MCP. Workspace searches are counted separately.
1 seat · 50 UI requests
Start free →3 seats · Unlimited UI requests
See plan details →10 seats · Unlimited UI requests
See plan details →25 seats · Unlimited UI requests
See plan details →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.
Try the free workspace, then connect your assistant with OAuth or your application with an API key.