REST + MCP

Build your first request.

The base URL is https://api.fccidapi.com. All data endpoints require a bearer API key.

Quickstart

  1. Create an account and API key.
  2. Store the key in your server environment as FCC_API_KEY.
  3. Send Authorization: Bearer YOUR_API_KEY with each request.

Keep keys out of URLs, source control and browser bundles. Revoking a key immediately blocks its integrations.

curl

curl --get https://api.fccidapi.com/v1/search \
  --data-urlencode "q=wireless" \
  --data-urlencode "has_details=true" \
  --data-urlencode "limit=20" \
  --header "Authorization: Bearer $FCC_API_KEY"
Python example
import json, os
from urllib.parse import urlencode
from urllib.request import Request, urlopen

query = urlencode({"q": "wireless", "has_details": "true", "limit": 20})
request = Request(
    f"https://api.fccidapi.com/v1/search?{query}",
    headers={"Authorization": "Bearer " + os.environ["FCC_API_KEY"]},
)
with urlopen(request, timeout=30) as response:
    page = json.load(response)
for application in page["applications"]:
    print(application["fcc_id"], application["grant_status"])
JavaScript example (server)
const query = new URLSearchParams({ q: "wireless", limit: "20" });
const response = await fetch("https://api.fccidapi.com/v1/search?" + query, {
  headers: { Authorization: "Bearer " + process.env.FCC_API_KEY },
});
if (!response.ok) throw new Error("FCC API returned " + response.status);
const page = await response.json();
console.log(page.applications);

Check the response

Expect HTTP 200 with an applications array and a nullablenext_cursor. An empty page is a valid result; it does not prove the device is absent from FCC records.

{
  "applications": [],
  "next_cursor": null
}

Example of an empty page. Actual responses also carry collection context; inspect the live OpenAPI schema for every field.

Endpoints

The API reference contains every endpoint, parameter, and schema. Thelive OpenAPI specification is the complete parameter and response reference.

MethodPathUse
GET/v1/searchFiltered applications and cursor pagination.
GET/v1/applications/{source_id}Collected details, grant notes, technical rows, exhibit links and evidence. URL-encode the source ID.
GET/v1/lookupExact or explained candidate matching: fccid, q, brand, manufacturer, model.
POST/v1/bulkBounded exact FCC ID lookup; paid responses include a CSV string.
GET/v1/frequencyFrequency overlap; lower_mhz and upper_mhz are required.
GET/v1/brandApplicant and historical grantee information; not consumer-brand verification.
GET/v1/exhibits/searchExhibit title and type metadata; no document text search.
GET/v1/exhibits/{id}Exhibit metadata and its upstream FCC location.
GET/v1/coverageCollected counts, gaps, source holds and collection checkpoints.

Filters & pagination

Filters combine with AND. q searches FCC IDs, applicant names and collected descriptions. fccid requests an exact FCC ID. grantee,country and equipment_class filter source values; country and class require exact values.

Use grant_status=granted|not_granted|unknown,has_details=true|false, inclusive from_date/to_datein YYYY-MM-DD format, and paired lower_mhz/upper_mhz bounds for overlapping frequency ranges.

Pages default to 25 applications, up to 100 with limit. Pass the returnednext_cursor as the next request’s cursor, keeping all original filters unchanged. URL-encode it. Stop when it is null. Each page consumes one unit. Results can change as imports continue.

Bulk lookup & CSV

curl https://api.fccidapi.com/v1/bulk \
  --header "Authorization: Bearer $FCC_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"fcc_ids":["ABC-DEVICE","XYZ-EXAMPLE"]}'

The IDs above are illustrative. Submit 1–5 distinct IDs on Free or 1–100 on a paid plan. Every submitted ID costs one API unit, including missing matches. The whole request is rejected before charging if validation or the remaining quota fails.

Each result contains its normalized fcc_id, status (foundor not_in_collected_corpus), up to ten recent applications, and a truncated flag. Use filtered search for the rest. There is no fuzzy matching in bulk lookup.

Paid responses also include csv, a quoted CSV string containing this bounded result and its source URLs. Free responses return null for CSV. Saving the returned CSV does not cost another unit. Formula-like cell prefixes are neutralized for spreadsheet safety.

MCP integration

Follow the connection guide for Claude, ChatGPT, Grok, Muse, and API-key clients →

Connect a remote MCP client to https://api.fccidapi.com/mcp using HTTP transport and the same bearer header. Use your client’s secret storage rather than committing the key in configuration.

Available tools are search_fcc, lookup_fcc_id, andget_application. They search applications, explain FCC-ID matches, and retrieve collected details. Use your client’s tool discovery for the exact schemas. MCP data calls share the REST allowance; initialization and discovery do not consume data units. See theworkspace MCP setup.

Usage & errors

Application errors return a JSON error code. For example:

{
  "error": "monthly_quota_exceeded"
}

All keys in an account share a monthly API allowance. MCP and REST share it too. UI searches and detail views use a separate allowance; the bulk UI uses API units. Resets occur on the first day of each UTC month, even on annual plans. Upgrades and downgrades do not reset counters.

A successful empty result counts. Invalid requests, rejected authentication and server failures do not consume monthly units. The x-ratelimit-remaining header reports remaining monthly units at admission.

StatusAction
400 / 422Correct the request before retrying.
401 / 403Check your key and account access.
404The record is absent from the collected corpus.
409The requested detail is held for source review.
429Read the error: wait for the rate window, or upgrade/wait for monthly reset. Respect Retry-After when present; monthly exhaustion does not reset after that delay.
5xxUse bounded retries with backoff.

Coverage & evidence

Coverage is incomplete. A missing record does not prove an FCC ID is invalid. Grant status is source metadata, not a compliance clearance.

Observation times describe our collection time, not FCC publication. Null details mean not collected; an empty exhibit list within collected details means the source listed no public exhibits at that observation. Applicant identity is not proof of a consumer brand or commercial model.

Saved searches show current matching metadata with changes recorded since your last review. They do not report records that stopped matching. Choose optional daily digests in Email alerts after signing in; your workspace admin controls alert permission and available seats. Historical discoveries may appear as new observations even when the underlying grant is old.

Preserve source URLs and hashes when using the evidence. PDF downloads, hosting, extraction, OCR, full-text search, customer webhooks are not part of the current service. Billing remains sandbox-only.