[Integrations](https://spiral.ai/integrations) › [n8n](https://spiral.ai/integrations/n8n) › [FCC certification body directory](https://spiral.ai/integrations/n8n/fcc-certification-body-directory)

# How to Use FCC certification body directory in n8n

Returns FCC-recognized telecommunications certification bodies. Use it to identify organizations that issue equipment certifications and distinguish them from laboratories that perform testing.

|  |  |
| --- | --- |
| Model | FCC certification body directory |
| Available through | Alexandria |
| Category | Lead Gen |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with FCC certification body directory in n8n

- Monthly, use FCC certification body directory to look for UL and report changes in the matching records.
- Every Monday at 9am: use FCC certification body directory to look this up and give me the result as a table.
- Pull the latest numbers from FCC certification body directory and tell me what changed since last week.
- Check FCC certification body directory and summarize what you find in three bullet points.
- Pull the newest data from FCC certification body directory and give me the result as a table.

## How to set up FCC certification body directory in n8n

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send n8n this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Create a key**: Create a key under API keys in the console.

2. **Add an MCP Client node**: In a workflow, add an MCP Client node (or, under an AI Agent node, an MCP Client Tool) and set:

```text
https://api.spiral.ai/mcp
```

3. **Pick a tool**: The node lists Spiral's tools. In an MCP Client node pick one, such as `run`, and give it its arguments:

```json
{
  "provider": "fal",
  "model": "fal-ai/flux/schnell",
  "input": { "prompt": "a lighthouse at dawn" },
  "wait": true
}
```

4. **Run FCC certification body directory in a workflow step**: Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds FCC certification body directory, prices it and runs it each time the step fires.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run FCC certification body directory**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "apps-fcc-gov/equipment-authorizations/list_tcbs",
    "input": {
      "city": "<city>"
    }
  }'
```

Then paste one of the prompts above: n8n finds FCC certification body directory on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/n8n

## FCC certification body directory tools and prices

- [FCC OET Equipment Authorization System (apps.fcc.gov) · List tcbs](https://spiral.ai/tools/alexandria/apps-fcc-gov/equipment-authorizations/list_tcbs) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| city |  | — | city |
| cursor |  | — | Continuation from a previous page (meta.page.next_cursor): the site's 1-based FromRec offset of the next page. |
| tcb_code |  | — | TCB code, e.g. US0101. |
| tcb_name |  | — | TCB name prefix. |
| page_size | 1 to 500 | 25 | Rows per page (the form's show_records; 500 accepted by the site). |
| tcb_scope |  | — | Scope code A1..A4, B1..B4. Pattern: ^[AB][1-4]$. |

## What can you do with FCC certification body directory in n8n?

Maintain a recurring FCC research digest for manufacturers and certification organizations you follow. A scheduled agent can compare returned records over time and surface changes for review.

### Build a hardware supplier review

Resolve a manufacturer's grantee records, find its device filings, and review grants and public exhibits. Check the certification bodies and testing firms involved to assemble a supplier evidence packet.

### Prepare a wireless module review

Compare candidate manufacturers and module filings, then read grant conditions and available supporting documents. Research the listed certification and testing organizations before preparing questions for a compliance review.

### Create a certification evidence register

Connect company records and FCC IDs to the relevant filings, grants, and public document lists. Add directory records for certification bodies and test firms so reviewers can trace the organizations behind the evidence.

### Research certification service candidates

Start with certification-body and test-lab directories, then inspect public filings for manufacturers in the device category you care about. Use grants and exhibits to investigate documented work before shortlisting organizations for further review.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All n8n guides](https://spiral.ai/integrations/n8n)

## FCC certification body directory in other agents

- [Amp](https://spiral.ai/integrations/amp/fcc-certification-body-directory)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/fcc-certification-body-directory)
- [Claude](https://spiral.ai/integrations/claude-desktop/fcc-certification-body-directory)
- [Claude Code](https://spiral.ai/integrations/claude-code/fcc-certification-body-directory)
- [Cline](https://spiral.ai/integrations/cline/fcc-certification-body-directory)
- [Codex](https://spiral.ai/integrations/codex/fcc-certification-body-directory)
- [Cursor](https://spiral.ai/integrations/cursor/fcc-certification-body-directory)
- [Devin](https://spiral.ai/integrations/devin/fcc-certification-body-directory)
- [dots](https://spiral.ai/integrations/dots/fcc-certification-body-directory)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/fcc-certification-body-directory)
- [Gemini](https://spiral.ai/integrations/gemini/fcc-certification-body-directory)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/fcc-certification-body-directory)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/fcc-certification-body-directory)
- [goose](https://spiral.ai/integrations/goose/fcc-certification-body-directory)
- [Grok](https://spiral.ai/integrations/grok/fcc-certification-body-directory)
- [Grok Build](https://spiral.ai/integrations/grok-build/fcc-certification-body-directory)
- [Hermes](https://spiral.ai/integrations/hermes/fcc-certification-body-directory)
- [Instinct](https://spiral.ai/integrations/instinct/fcc-certification-body-directory)
- [Manus](https://spiral.ai/integrations/manus/fcc-certification-body-directory)
- [Muse](https://spiral.ai/integrations/muse/fcc-certification-body-directory)
- [Muse Code](https://spiral.ai/integrations/muse-code/fcc-certification-body-directory)
- [Notion](https://spiral.ai/integrations/notion/fcc-certification-body-directory)
- [OpenClaw](https://spiral.ai/integrations/openclaw/fcc-certification-body-directory)
- [opencode](https://spiral.ai/integrations/opencode/fcc-certification-body-directory)
- [Perplexity](https://spiral.ai/integrations/perplexity/fcc-certification-body-directory)
- [Raycast](https://spiral.ai/integrations/raycast/fcc-certification-body-directory)
- [VS Code](https://spiral.ai/integrations/vscode/fcc-certification-body-directory)
- [Windsurf](https://spiral.ai/integrations/windsurf/fcc-certification-body-directory)
- [Zapier](https://spiral.ai/integrations/zapier/fcc-certification-body-directory)

## More n8n guides

- [FCC application exhibits](https://spiral.ai/integrations/n8n/fcc-application-exhibits)
- [FCC equipment authorization search](https://spiral.ai/integrations/n8n/fcc-equipment-authorization-search)
- [FCC ID filings](https://spiral.ai/integrations/n8n/fcc-id-filings)
- [FCC equipment grant](https://spiral.ai/integrations/n8n/fcc-equipment-grant)
- [Enrow work email finder](https://spiral.ai/integrations/n8n/enrow-work-email-finder)
- [FCC grantee search](https://spiral.ai/integrations/n8n/fcc-grantee-search)

## Questions about FCC certification body directory in n8n

**Can n8n use FCC certification body directory?**

Yes. Add Spiral to n8n as an MCP server, and n8n can find and run FCC certification body directory like any built-in tool.

**How much does FCC certification body directory cost in n8n?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your n8n plan is separate.

**Do I need an Alexandria account to use FCC certification body directory in n8n?**

You need no Alexandria account. n8n uses one Spiral API key for every tool, and Spiral runs FCC certification body directory on its own Alexandria account.

**How long does it take to set up FCC certification body directory in n8n?**

About two minutes: create a key, then add an MCP Client node, then pick a tool.

**Does n8n wait while FCC certification body directory runs?**

FCC certification body directory runs in the background. n8n starts the run, checks on it and gives you the json when it's ready.

**Does the FCC database cover every electronic product?**

No. EAS contains certification applications and grants, while equipment authorized through Supplier's Declaration of Conformity ordinarily requires no submission of compliance data to the FCC.

**When does certification information become public?**

Supporting information becomes public upon grant of the equipment authorization, subject to confidentiality restrictions. Pending requests are excluded from disclosure before the authorization takes effect.

**Are all filing documents available to read?**

Public documents can include test reports, photos, and manuals. Confidential exhibits can be withheld, so the public record may not expose every document submitted for certification.

**How is an FCC ID structured?**

It combines a three-character or five-character grantee code with a product code of up to 14 characters. The product code can include a hyphen, which should be preserved.

**What is the difference between a test lab and a certification body?**

Test laboratories produce compliance testing evidence. Telecommunications certification bodies evaluate application data and test reports and make certification decisions.

