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.
Find wireless devices with collected application details.
search_fccOpen a result to inspect its technical details and source links.
Look up [FCC ID] and show me its application history.
lookup_fcc_idInspect match details before treating a suggested FCC ID as an exact match.
Show the public exhibit links for [application ID].
get_applicationOpen the upstream FCC documents. Review the original filing alongside its metadata.
Search by FCC ID, company or product keyword. No account needed.
Want filters, favorites and API access? Create your free account →
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 →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.
fcc_idapplicant_namegrantee_codeproduct_codepurposegrant_statusaction_dateFind an FCC ID, its applicant, and the applications we have collected. Filter by applicant, country, date, and grant status.
Explore the documentation →frequencies.lower_mhzfrequencies.upper_mhzprofiledetailsSearch overlapping frequency ranges and inspect collected equipment details. Read frequency ranges alongside the application’s equipment classification.
Explore the documentation →attachment_idtitleexhibit_typefile_typeurlRead exhibit metadata and follow original FCC document locations. Find test reports, manuals and other public filings at their original source.
Explore the documentation →source_idform_urlgrant_urlexhibits_urlKeep source links and observation dates beside the data, so your research stays connected to the original FCC records.
Explore the documentation →Favorite devices, save repeat searches, and get optional daily email alerts for observed changes. Your workspace keeps research together.
Sign in with your email, approve read access, and start asking. REST and every connected assistant share one API allowance.
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 →Use this server URL and select OAuth.
https://api.fccidapi.com/mcp
Use your FCC ID API email code. Check the workspace and allow read access.
“Search for wireless devices and show me the collected source links.”
Add a custom web connector with OAuth sign-in. Leave the client ID and secret blank for automatic setup.
Full Claude setup guide →Use this server URL and select OAuth.
https://api.fccidapi.com/mcp
Use your FCC ID API email code. Check the workspace and allow read access.
“Search for wireless devices and show me the collected source links.”
Add a custom connector and select OAuth. Grok and the xAI console use the same FCC ID API server.
Full Grok setup guide →Use this server URL and select OAuth.
https://api.fccidapi.com/mcp
Use your FCC ID API email code. Check the workspace and allow read access.
“Search for wireless devices and show me the collected source links.”
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 →Use this server URL and select OAuth.
https://api.fccidapi.com/mcp
Use your FCC ID API email code. Check the workspace and allow read access.
“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.
Source URLs, observation times, and original filings help you understand what a record tells you.
Explore the data documentation →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.
Try the free workspace, then connect your assistant with OAuth or your application with an API key.