Healthcare.gov Content API

Name: Healthcare.gov Content API
Brand: Healthcare.gov Content API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareClinical Datanone16 EndpointsREST

For Agents

Fetch consumer health content from healthcare.gov — articles, glossary terms, blog posts, FAQ questions, state pages, and topics — in English or Spanish.

Install Jentic One Beta

Connect the Healthcare.gov Content API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Healthcare.gov Content API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Healthcare.gov Content API.

List published articles from healthcare.gov via /api/articles{mediaTypeExtension}

Retrieve glossary entries by slug through /glossary/{pageName}{mediaTypeExtension}

Fetch FAQ questions and answers through /api/questions and /question/{pageName}

GET STARTED

Start building with Healthcare.gov Content API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Healthcare.gov Content API for, with concrete tasks.

★ Plan-Finder Educational Content

Health insurance plan-finder apps embed healthcare.gov articles and glossary entries to explain coverage terms inline, rather than linking out and losing the user. The /api/glossary and /api/articles endpoints return curated, official content that teams can render in their own UI. The Spanish endpoints under /es/ make it straightforward to launch a bilingual experience.

GET /api/articles.json and render the title and url for the latest five articles in a sidebar

State-Level Insurance Information Pages

Apps that route users to state-specific marketplaces use /api/states and /{stateName}{mediaTypeExtension} to pull the official healthcare.gov state page for a given state. This gives a current, consistent view of what each state offers without manually maintaining 50 entries. Spanish equivalents under /es/{stateName} are available for bilingual rollouts.

GET /api/states.json and follow the result to /{stateName}.json for a specific state to render its full page content

FAQ and Glossary Search

Customer-support agents and chatbots search the healthcare.gov FAQ and glossary endpoints to answer common questions like what counts as a qualifying life event or how subsidies are calculated. The /api/questions and /api/glossary list endpoints provide the index, and the per-slug endpoints return the full page content for the matching item. The result is grounded answers rather than freeform text.

GET /api/questions.json, find the entry matching the user's question, and fetch /question/{pageName}.json for the full answer

AI Agent Health Content via Jentic

Agents search Jentic for 'look up a health insurance term' and Jentic returns the relevant healthcare.gov glossary or article operation. The agent can then fetch grounded content for use in summaries, citations, or chat replies. Because the API is unauthenticated, no vault credentials are needed, but Jentic still wraps the call with rate-limit handling and consistent response shapes.

Use Jentic search 'look up a health insurance term' to load /glossary/{pageName}.json and execute for the slug 'premium-tax-credit'

Key Endpoints

16 endpoints — the healthcare.

METHOD

PATH

DESCRIPTION

GET

/api/articles{mediaTypeExtension}

List articles

GET

/api/blog{mediaTypeExtension}

List blog posts

GET

/api/glossary{mediaTypeExtension}

List glossary entries

GET

/api/questions{mediaTypeExtension}

List FAQ questions

GET

/api/states{mediaTypeExtension}

List state pages

GET

/api/topics{mediaTypeExtension}

List topics

GET

/glossary/{pageName}{mediaTypeExtension}

Read a glossary entry

GET

/{pageName}{mediaTypeExtension}

Fetch a specific content page

GET

/api/articles{mediaTypeExtension}

List articles

GET

/api/blog{mediaTypeExtension}

List blog posts

GET

/api/glossary{mediaTypeExtension}

List glossary entries

GET

/api/questions{mediaTypeExtension}

List FAQ questions

GET

/api/states{mediaTypeExtension}

List state pages

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Healthcare.gov Content API is unauthenticated. Jentic still wraps the call so agents share a uniform request and response format with other tools.

Intent-based discovery

Agents search Jentic for intents like 'look up a health insurance term' or 'list healthcare.gov articles' and Jentic returns the matching content operation.

Time to first call

Direct integration: 1-2 hours to wire URL templates and media type extensions. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using Healthcare.gov Content API through Jentic.

What authentication does the Healthcare.gov Content API use?

The API is fully public and does not require authentication. The spec defines no security schemes, so calls work with a plain HTTP GET and the desired media type extension.

Can I retrieve content in Spanish?

Yes. Every content path has a Spanish equivalent under /es/, including /es/blog/{pageName}, /es/glossary/{pageName}, /es/question/{pageName}, and /es/{stateName}. Use the same media type extension as the English endpoints.

What media types does the API return?

Each path takes a {mediaTypeExtension} segment. Append .json for JSON; the spec returns content as static JSON files served from www.healthcare.gov, so caching at the client side is straightforward.

What are the rate limits for the Healthcare.gov Content API?

Healthcare.gov does not publish a per-IP rate limit for content endpoints, but the content is served as static JSON behind a CDN. Cache responses aggressively rather than refetching on every request.

How do I look up a healthcare.gov glossary term through Jentic?

Search Jentic for 'look up a health insurance term', load the /glossary/{pageName}.json operation for healthcare.gov, and execute with the term slug. Jentic returns the title and definition for use in your reply.

Is the Healthcare.gov Content API free?

Yes. Healthcare.gov is a US government service and the content endpoints are free to use under the public domain content guidelines published on the site.