API
Search public records across healthcare, procurement, sanctions, enforcement, and company-register domains, with nullable source and observation context defined by each response contract.
Open API→The surfaces
Pick your integration path
API reference
Endpoint-by-endpoint reference for the /api/v1 surface: auth, rate limits, the freshness contract, and the response envelope.
Open API reference→MCP server
A nine-tool Model Context Protocol server for read-only lookup, search, screening, source discovery, and snapshot re-checks, with four citation-context keys on every tool response.
Open MCP server→FHIR R4 API
HL7 FHIR R4 US Core 6.1.0: Practitioner, Organization, Location, PractitionerRole, HealthcareService, with SMART Backend Services auth and Bulk $export.
Open FHIR R4 API→SDKs & integrations
A Python SDK, an npm package, and framework adapters — plus the screening CLI and GitHub Action that fail a build when a tracked NPI is excluded.
Open SDKs & integrations→Bulk export
Manifest-led downloads: each listed file has a delivered schema, filename, and compression format.
Open Bulk export→Webhooks
Subscribe to provenance-stamped provider events. HMAC-SHA256-signed POSTs fire when LEIE or PECOS state changes for a tracked provider.
Open Webhooks→Quickstart
The fastest path in: an issued API key, a first read, and the bulk manifest.
Open Quickstart→Reference & operations
Docs, status, and changelog
Documentation home
Every guide, reference, and spec in one index.
Status
Live availability and incident history.
Changelog
Dated, one-line entries for every shipped change.
The Terminal
Search the resolved entity graph in the browser before writing a line of code.
Developer use cases
FHIR R4, bulk export, and the MCP server mapped to concrete build patterns.
Developer FAQ
Common questions
- What developer surfaces does Fonteum offer?
- Four ways in: a REST API for direct queries, an MCP server for AI agents, an HL7 FHIR R4 interface for clinical interoperability, and bulk export for whole-dataset downloads. SDKs, a screening CLI, and a GitHub Action wrap those surfaces for common workflows.
- Do I need to authenticate to start?
- REST and MCP examples use an issued FONTEUM_API_KEY with Bearer authentication. See the authentication guide for the current access and rate-limit policy.
- What public records power the developer APIs?
- The active production registry spans healthcare, procurement, sanctions and watchlists, federal enforcement, intellectual property, securities filings, and global company registers. Responses carry source and observation context where the route and underlying evidence supply it; those fields can be null. Active registry status does not itself mean every family has loaded, complete, fresh, or displayable records.
- How does the screening CLI and GitHub Action work?
- The CLI screens a list of NPIs against the exclusion lists and exits non-zero on a match; the GitHub Action runs it in CI so a workforce or vendor change that introduces an excluded provider fails the build. Both return the matching list, the exclusion date, and the source citation.
- Is freshness exposed in the API?
- Freshness is source-specific. Responses can expose snapshot and last-checked dates where the route and source supply them; those fields may be null or absent. Consult the returned payload and endpoint documentation rather than inferring a universal SLA or fail-closed policy.
- Can I get the data in bulk instead of per request?
- The machine-readable bulk manifest lists only files that are currently delivered, including their filename, media type, compression, and columns. Do not infer a bulk format from a source page; use the manifest as the availability contract.
START BUILDING
Call the API or drop the MCP server into your agent.
Grab a sandbox key, make a first FHIR read, or screen an NPI from the CLI. Provenance rides on every field — no contract to begin.