Skip to content
FonteumThe Graph

By use case

Exclusion & monitoring (self-serve)Free roster screen — no accountExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskJournalists & newsroomsDevelopers & AI teams

By industry

HealthcareProviders & facilitiesSanctionsOFAC / EU / UK / UN / OIG / SAMFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessFor AI agentsModel Context Protocol serverFHIR R4 APIBulk exportAudit packSigned report artifacts; source facts remain separately citedReconciliationSource-vs-source diffsAI answers with sourcesHow records link upHistoryRetained versions for named sources

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityAI answers, comparedBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceConnect your AI agent (MCP)One-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

Solutions

Exclusion & monitoring (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teamsHealthcareSanctionsFederal contracting

Platform

APIFor AI agentsFHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory

Data

Coverage & sourcesFreshnessMethodologyCare CompareAI answers, comparedBrowse all datasets →
Research

Developers

DocsAPI referenceConnect your AI agent (MCP)FHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →
  1. Fonteum
  2. /
  3. Glossary
  4. /
  5. FRN
Fonteum Data GlossaryData Standards

What is an FRN?

An FRN is a 10-digit FCC Registration Number assigned through the Commission Registration System to people or entities doing business with the Federal Communications Commission. It identifies the registrant in FCC filings, fees, licenses, auctions, and other transactions; it is not the same thing as an FCC ID for equipment.

Full name: FCC Registration Number

Short explanation

The FCC Registration Number is the Commission's registrant identifier for entities and individuals that interact with FCC systems. Federal rules require an FRN for many filings, feeable transactions, license applications, and auction activities. In data work, the FRN identifies the party doing business with the FCC, while call signs, application file numbers, facility IDs, and FCC IDs identify different records.

Related platform: Entity graph - resolved organization records

Last updated: 2026-07-11Reviewed by: Fonteum data standards desk — Source-provenance editorial review. Definitions checked against primary federal sources.

How it’s used

  • FCC filings: an FRN ties a filing, payment, license application, or auction transaction to the registrant in FCC systems.
  • Entity resolution: FRN is a source-local FCC party key and should not be confused with equipment identifiers, radio call signs, or application file numbers.
  • Fonteum treats FRN as a federal identifier family that can link communications-regulatory records to an organization-level entity graph.

Frequently asked questions

How many digits are in an FRN?
An FRN is a 10-digit FCC Registration Number.
Who needs an FRN?
People and entities doing business with the FCC may need an FRN for filings, fees, license applications, auctions, and other FCC transactions.
Is an FRN the same as an FCC ID?
No. An FRN identifies a registrant doing business with the FCC; an FCC ID identifies equipment covered by an equipment authorization.

Related terms

  • FCC ID
  • Entity Resolution
  • Provenance
  • ABN vs ACN
  • SIREN vs SIRET
  • UEI

Explore in Fonteum

How Fonteum sources, resolves, and publishes data tied to this term.

  • PlatformEntity graph - resolved organization records
  • Use caseFederal contracting and regulatory data hub
  • PlatformSource provenance model

Authoritative sources

  • eCFR: 47 CFR Part 1 Subpart W - FCC Registration Number↗
  • Federal Register: mandatory FCC Registration Number↗
← All glossary terms

What’s on file, by the numbers

Platform snapshot · 2026-07-15

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
—sources liveCrosswalk-resolved sources with a proved content transition in the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Published figures name their source and date.

Source and date

Published research identifies its government file and observation date. Source-file SHA-256 coverage is disclosed separately; facts do not currently link deterministically to signatures.

Reproducible SQL

Each study ships the exact query behind its figures, run against the same dated copy of the federal file we used. Re-run it yourself.

Daily observations

The platform records table row counts daily. Those observations detect local drift; they do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Fonteum
Platform
Platform overviewAPIFor AI agents (MCP)FHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGUse casesM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareNursing homesRecall recordsSanctions screeningOIG LEIE listOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubLearnHow it worksGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsSourced data vs plain LLM answersCitationsManifestoWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI termsMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

A public-records graph that exposes source and observation metadata where supplied.

Fonteum's provenance ledger contained 26.2M source-linked facts on July 12, 2026. All but 14 carried a source-file SHA-256; 0 linked deterministically to a signature. Inspect a supplied snapshot id at fonteum.com/verify · source-mark coverage and limitations.
Request access→