Install Jentic One Beta

Connect the HealthData.gov Socrata Open Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HealthData.gov Socrata Open Data 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%2Fhealthdata.gov%2Fhealthdata" | 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%2Fhealthdata.gov%2Fhealthdata" | 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 HealthData.gov Socrata Open Data API.

Search and browse the dataset catalog to find relevant health datasets

Query a specific dataset with SoQL, filtering and aggregating rows server-side

Retrieve query results as JSON or CSV for direct loading into analysis tools

Fetch a dataset's metadata to understand its columns before querying

GET STARTED

Start building with HealthData.gov Socrata Open Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HealthData.gov Socrata Open Data API for, with concrete tasks.

★ Agent-Driven Health Data Queries

An AI agent answering a health question finds the right dataset through the HealthData.gov catalog, then queries it with SoQL to pull only the rows it needs. Through Jentic the agent calls the catalog and resource endpoints directly, returning JSON it can reason over without a developer scripting the Socrata query flow.

Search the catalog for a hospital capacity dataset, then query its resource endpoint with a SoQL filter for one state

Loading Health Datasets into Analytics Tools

Analysts pull government health data into notebooks and dashboards. The HealthData.gov API returns query results as JSON or CSV, so a pipeline can request a filtered slice of a dataset and load it directly without scraping the portal interface.

Query a dataset's CSV endpoint with a date filter and load the result into a dataframe

Dataset Discovery and Schema Inspection

Before querying, a workflow needs to know what datasets exist and what columns they carry. The HealthData.gov catalog endpoint lists available datasets and the views metadata endpoint returns a dataset's schema, so an agent can pick the right dataset and build a valid SoQL query.

List catalog datasets matching 'Medicare', then fetch the metadata for the top result to read its columns

Key Endpoints

5 endpoints — the healthdata.

METHOD

PATH

DESCRIPTION

GET

/api/catalog/v1

Search the dataset catalog

GET

/resource/{datasetId}.json

Query a dataset with SoQL, returning JSON

GET

/resource/{datasetId}.csv

Query a dataset, returning CSV

GET

/api/views/{datasetId}.json

Get metadata for a dataset

GET

/api/views/{datasetId}/rows.json

Get rows via the legacy views API

GET

/api/catalog/v1

Search the dataset catalog

GET

/resource/{datasetId}.json

Query a dataset with SoQL, returning JSON

GET

/resource/{datasetId}.csv

Query a dataset, returning CSV

GET

/api/views/{datasetId}.json

Get metadata for a dataset

GET

/api/views/{datasetId}/rows.json

Get rows via the legacy views API

Why Jentic?

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

Setup

Wiring HealthData.gov by hand means learning SoQL, discovering dataset ids through the catalog, and optionally registering an app token for the X-App-Token header. Through Jentic you install once, import the HealthData.gov Socrata API from the API Directory, store the optional token once, and your agent calls it.

Permission scoping

The dataset id travels in the URL path (/resource/{datasetId}.json), so a rule can pin your agent to specific datasets, and every operation here is read-only. You choose the operations it may call, so it queries and reads catalog data and nothing else unless you add more.

Credential isolation

Your optional Socrata app token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'query a health dataset', and Jentic returns the matching Socrata operation with its input schema so the agent builds a valid SoQL request without browsing the portal.

FAQs

Specific to using HealthData.gov Socrata Open Data API through Jentic.

What authentication does the HealthData.gov Socrata API use?

The HealthData.gov Socrata Open Data API accepts an optional application token passed in the X-App-Token header, per its OpenAPI spec. Public datasets can be queried without a token, but registering one raises your rate limits. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

Is there a HealthData.gov Socrata API MCP server?

You don't need an MCP server to give your agent the HealthData.gov Socrata API. Jentic connects it directly from the API Directory: import it, store your optional app token once, and your agent searches the catalog and queries datasets as it needs them. Nothing extra is loaded into the agent's context until a call is made.

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

Yes. Every operation here is read-only, and you choose which ones your agent may call, so you can allow catalog search and dataset queries and nothing else. Every call it makes is logged, so you can see which datasets it read.

Can I query a specific dataset with SoQL through the HealthData.gov API?

Yes. The resource endpoint accepts SoQL, the Socrata Query Language, so an agent can filter, select, and aggregate rows server-side and receive only the data it needs as JSON or CSV.

What are the rate limits for the HealthData.gov Socrata API?

Public requests are throttled by Socrata, and registering an app token to send in the X-App-Token header raises the limit. The OpenAPI spec does not state exact numbers, so check the Socrata documentation at https://dev.socrata.com for current throttling rules.

How do I query HealthData.gov datasets through Jentic?

Search Jentic for 'query a health dataset', which returns the resource query operation with its input schema. Add the HealthData.gov Socrata API from the Jentic API Directory and store your optional app token once. To run it on your own infrastructure, install Jentic One from its GitHub repo.

HealthData.gov Socrata Open Data API

Name: HealthData.gov Socrata Open Data API
Brand: HealthData.gov Socrata Open Data API
Availability: InStock

Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceOptional Socrata app token (X-App-Token header)5 EndpointsREST

For Agents

Discover U.S. health datasets through the catalog and query them with SoQL, returning filtered JSON or CSV results for analysis.

Use for: Find datasets about hospital capacity on HealthData.gov, Query a COVID-19 dataset for a specific state, Get the column metadata for a dataset before querying it, Download a health dataset as CSV

Not supported: Does not write, upload, or modify datasets, and does not host non-health data. Use for discovering and querying HealthData.gov's public health datasets only.

The HealthData.gov Socrata Open Data API provides programmatic access to U.S. health datasets published by HHS, CDC, CMS, and other agencies, covering topics from COVID-19 and hospital capacity to Medicare and community health. Agents discover datasets through the catalog endpoint and query individual datasets with SoQL, the Socrata Query Language, returning results as JSON or CSV. An optional app token in the X-App-Token header raises rate limits but is not required for public data.

Jentic One on Github View OpenAPI Document