CDC
The US Centers for Disease Control and Prevention (CDC) provides a suite of public APIs for accessing disease surveillance data, vaccination rates, health statistics, environmental public health tracking, and public health datasets. Key offerings include the CDC WONDER API for querying mortality and disease databases, the Open Data API powered by Socrata for thousands of datasets across categories such as flu vaccinations, STDs, injury, and NCHS statistics, the Environmental Public Health Tracking Network API for environmental health data, and the PHIN VADS vocabulary service for public health terminology.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles CDC the way a machine reads it — 19 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — CDC scores 37.0/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile CDC
Each block below is one kind of artifact we hold for CDC. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
CDC WONDER API
The CDC WONDER (Wide-ranging Online Data for Epidemiologic Research) API enables automated data queries in XML format over HTTP. Supports access to online databases covering mor...
CDC Environmental Public Health Tracking Network API
Allows querying of data from the CDC National Environmental Public Health Tracking Network. Returns JSON-formatted responses covering environmental health indicators such as air...
CDC Content Syndication API
Enables CDC to offer web content to other sites and applications. Provides structured access to CDC health content including articles, health topics, media, and tools in JSON an...
PHIN VADS API
The Public Health Information Network Vocabulary Access and Distribution System (PHIN VADS) is a web-based enterprise vocabulary system for accessing, searching, and distributin...
CDC app-notifications API
The app-notifications API from CDC — 1 operation(s) for app-notifications.
CDC code-systems API
The code-systems API from CDC — 1 operation(s) for code-systems.
CDC conditions API
The conditions API from CDC — 2 operation(s) for conditions.
CDC configurations API
The configurations API from CDC — 15 operation(s) for configurations.
CDC events API
The events API from CDC — 2 operation(s) for events.
CDC Query API
The Query API from CDC — 1 operation(s) for query.
CDC Query Connector API OpenAPI 3.0 API
The Query Connector API OpenAPI 3.0 API from CDC — 1 operation(s) for query connector api openapi 3.0.
CDC releases API
The releases API from CDC — 1 operation(s) for releases.
CDC simulator API
The simulator API from CDC — 3 operation(s) for simulator.
CDC user API
The user API from CDC — 1 operation(s) for user.
Scroll within the panel for all 14 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for CDC — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/cdc · machine-readable index on apis.io