Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bureau of Labor Statistics Public 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%2Fbls.gov%2Fbls" | shStep 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%2Fbls.gov%2Fbls" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Bureau of Labor Statistics Public Data API.
Retrieve data for one or more time series
Retrieve a single time series or just its latest value
List the available BLS surveys
Retrieve the most popular time series
Patterns agents use Bureau of Labor Statistics Public Data API for, with concrete tasks.
GET STARTED
★ Pull labour statistics
Bring official United States labour figures into an agent workflow. The agent requests the observations for one or more time series and reads them back as structured data.
Call POST /timeseries/data/ with the series ids to retrieve
Track a single indicator
Watch one indicator closely. The agent reads a single series or just its latest observation so it can report the current figure without pulling the full history each time.
Call GET /timeseries/data/{seriesId}/latest for the indicator
Discover available data
Find out what BLS publishes before querying it. The agent lists the surveys and reviews the most popular series to pick the right data to pull.
Call GET /surveys, then GET /timeseries/popular to choose a series
5 endpoints — jentic publishes the only available openapi specification for bureau of labor statistics public data api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/timeseries/data/
Retrieve data for one or more time series
/timeseries/data/{seriesId}
Retrieve data for a single time series
/timeseries/data/{seriesId}/latest
Retrieve the latest observation for a time series
/timeseries/popular
Retrieve popular time series
/surveys
List available BLS surveys
/timeseries/data/
Retrieve data for one or more time series
/timeseries/data/{seriesId}
Retrieve data for a single time series
/timeseries/data/{seriesId}/latest
Retrieve the latest observation for a time series
/timeseries/popular
Retrieve popular time series
/surveys
List available BLS surveys
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the BLS Public Data API by hand means registering for a key, pointing at the api.bls.gov host, and shaping the time-series requests yourself. Through Jentic you install once, import the BLS Public Data API from the Jentic API Directory, store the key once, and your agent calls it.
Permission scoping
The BLS Public Data API is read-only, so nothing can be mutated. You choose which of the five operations your agent may call, and because the series id sits in the URL path (/timeseries/data/{seriesId}), a rule can pin the agent to one series and nothing else.
Credential isolation
Your BLS registration key, passed as the registrationkey query parameter, 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 'get the latest value for a BLS series' or 'list BLS surveys', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference.
Alternatives and complements available in the Jentic catalogue.
Specific to using Bureau of Labor Statistics Public Data API through Jentic.
Why is there no official OpenAPI spec for the BLS Public Data API?
The Bureau of Labor Statistics publishes the Public Data API but does not ship a machine-readable OpenAPI description for it. Jentic wrote and validated one so agents can discover and call the service. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What authentication does the BLS Public Data API use?
The BLS Public Data API uses a registration key supplied as the registrationkey query parameter. Through Jentic, that key is stored encrypted in your Jentic One instance and injected at execution time, so the raw key never enters the agent context.
What can an agent do with the BLS Public Data API?
It can retrieve observations for one or more time series, read a single series or its latest value, list the available surveys, and pull the most popular series. Responses are structured so an agent can parse and act on them directly.
What are the rate limits for the BLS Public Data API?
Rate limits are not specified in the OpenAPI spec. Check the Bureau of Labor Statistics documentation for current limits. Through Jentic, retries are handled in the execution layer.
How many endpoints does the BLS Public Data API have?
The BLS Public Data API exposes 5 endpoints covering time series, surveys, and popular series.
Can I limit what my agent is allowed to do with the BLS Public Data API?
Yes. Jentic One is self-hosted by you, so your own rules decide which BLS operations your agent may call. The service is read-only, so nothing can be mutated, and because the series id sits in the URL path, such as /timeseries/data/{seriesId}, a rule can pin the agent to a single series and nothing else.
Know of an official OpenAPI document? Contribute it →
For Agents
Query United States labour statistics from the BLS Public Data API: time series, latest values, surveys, and popular series. Secured with a registration key.
Use for: Get BLS data for a time series, Retrieve the latest value for a series, List the available BLS surveys, Find the most popular BLS series
Not supported: Does not handle data visualization or any write operations - use it for reading Bureau of Labor Statistics data only.
Jentic publishes the only available OpenAPI specification for Bureau of Labor Statistics Public Data API, keeping it validated and agent-ready. The BLS Public Data API serves official United States labour statistics. An agent can retrieve observations for one or more time series, read a single series or just its latest value, list the available surveys, and pull the most popular series. It covers employment, wages, inflation, and productivity figures published by the Bureau of Labor Statistics.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>