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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhealthcare.gov%2Fhealthcaregov" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhealthcare.gov%2Fhealthcaregov" | 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}

Access state-by-state health insurance information via /api/states and /es/{stateName} for Spanish

GET STARTED

Start building with Healthcare.gov Content API

Explore with Jentic One

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

GET

/api/topics{mediaTypeExtension}

List topics

GET

/glossary/{pageName}{mediaTypeExtension}

Read a glossary entry

GET

/{pageName}{mediaTypeExtension}

Fetch a specific content page

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

The Healthcare.gov Content API needs no credential, so wiring it by hand is mostly handling its media-type path extensions and reconciling responses with your other tools. Through Jentic you install once, import the Healthcare.gov Content API from the API Directory, and your agent calls it with a consistent request and response shape.

Permission scoping

The Content API is read-only and unauthenticated, with fetches spread across endpoints like /api/articles, /api/glossary, and /api/topics, so limit the agent to the content fetches it needs, such as looking up an insurance term or listing articles. You choose the operations it may call, so anything outside that set is not included unless you add it.

Credential isolation

The Healthcare.gov Content API is unauthenticated, so there is no credential to store or inject. Jentic still routes the call through your own Jentic One instance so it shares a consistent execution surface with your other tools.

Intent-based discovery

Agents search Jentic by intent such as 'look up a health insurance term' or 'list healthcare.gov articles', and Jentic returns the matching content operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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.

Can I limit what my agent is allowed to do with the Healthcare.gov Content API?

Yes. Because you run Jentic One yourself, you decide which of the Content API's read operations your agent may call, so you can allow only the fetches it needs, such as listing articles via /api/articles or looking up a term via /api/glossary and /glossary/{pageName}, while leaving out /api/topics, /api/states, or the blog and question endpoints. The API is read-only and unauthenticated, so there are no credentials to hand over, and any operation you do not add stays out of the agent's reach. This keeps the agent scoped to the exact content lookups your own rules permit.

Healthcare.gov Content API

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

Community OpenAPI document · agent-readyHealthcareClinical Datanone16 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: Get the list of articles published on healthcare.gov, Look up a healthcare.gov glossary term by slug, Retrieve a specific FAQ question and its answer, List all states covered by healthcare.gov content

Not supported: Does not handle plan enrollment, eligibility checks, or subsidy calculations - use for read-only fetches of healthcare.gov consumer content only.

The Healthcare.gov Content API exposes the public consumer-facing content on healthcare.gov as JSON, including articles, blog posts, glossary entries, FAQ questions, state-level information, and topic listings, with parallel Spanish (/es/) endpoints. Each path returns either a list resource (such as articles or topics) or a specific page by slug, in the requested media type extension. Health insurance plan-finder apps, education sites, and accessibility tools use it to surface official healthcare.gov content without scraping the website.

Jentic One on Github View OpenAPI Document