Getting started

FDA Intel developer docs

FDA inspection intelligence for AI assistants and your own code: Form 483s, EIRs, warning letters, FDA investigators and 21 CFR citations, plus FDA public data on inspections, import alerts, recalls and registrations. 27 read-only tools, two simple plans.

Choose how to connect#

Both ways use the same tools, the same data and the same plan allowance. Pick by who is asking the questions.

Who uses itMCP: AI assistants: Claude, ChatGPT, Claude Code, Cursor, VS Code, agentsREST: Your code: scripts, internal tools, BI and data pipelines
Sign-inMCP: OAuth in a browser window (or an API key header)REST: An API key from your account page, as a Bearer token
AddressMCP: https://fdaintel.ai/mcpREST: https://fdaintel.ai/api/intel/v1
You getMCP: Answers in chat, with the documents linkedREST: JSON you can store, join and chart

Addresses#

MCP server
https://fdaintel.ai/mcp
REST API base URL
https://fdaintel.ai/api/intel/v1
MCP server card
https://fdaintel.ai/.well-known/mcp.json
OAuth metadata
https://fdaintel.ai/.well-known/oauth-protected-resource/mcp

Before you start#

You need an FDA Intel account with a Standard or Premium plan (from $78/month, billed yearly): compare plans, then start one on your account page. The same page shows your MCP address, creates API keys and shows live usage.

Your first call#

A site's current FDA standing by FEI number, over REST. In an AI assistant, ask "What is the FDA standing of FEI 3001234567?" and it calls the same tool.

curl "https://fdaintel.ai/api/intel/v1/call/facility_signal?fei=3001234567" \
  -H "Authorization: Bearer $FDA_INTEL_API_KEY"

What the tools cover#

Every tool is read-only. Plans cover data: metadata, summaries, profiles, citations and the opening words of each observation, with each document's link. Document text and PDFs are not part of the API; full documents are bought and downloaded on the site.