Install Jentic One Beta

Connect the Australian Bureau of Statistics Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Australian Bureau of Statistics 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%2Fabs.gov.au%2Fabs" | 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%2Fabs.gov.au%2Fabs" | 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 Australian Bureau of Statistics Data API.

Retrieve statistical data for a chosen dataflow and data key

List all available ABS dataflows

Get the details of a single dataflow

Get a data structure definition

Get codelist values

GET STARTED

Start building with Australian Bureau of Statistics Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Australian Bureau of Statistics Data API for, with concrete tasks.

★ Read official Australian statistics

Pull published Australian Bureau of Statistics figures straight into an agent workflow. The agent lists the available dataflows, picks the one it needs, and reads the series for a given data key.

Call GET /dataflow/ABS to list dataflows, then GET /data/{dataflow_id}/{data_key} for the series

Resolve dataflow metadata

Make raw statistical codes human-readable. The agent fetches a dataflow's data structure, then resolves its codelists and concept schemes so dimension values can be labelled correctly.

Call GET /datastructure/ABS/{structure_id}, then GET /codelist/ABS/{codelist_id} to label the dimensions

Monitor an economic indicator

Track a specific indicator over time. The agent reads the same dataflow and data key on a schedule and compares the latest observations against previous runs.

Call GET /data/{dataflow_id}/{data_key} on a schedule and diff the latest values

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for australian bureau of statistics data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/data/{dataflow_id}/{data_key}

Get statistical data for a dataflow and data key

GET

/dataflow/ABS

List all available dataflows

GET

/dataflow/ABS/{dataflow_id}

Get dataflow details

GET

/datastructure/ABS/{structure_id}

Get a data structure definition

GET

/codelist/ABS/{codelist_id}

Get codelist values

GET

/conceptscheme/ABS/{scheme_id}

Get a concept scheme

GET

/data/{dataflow_id}/{data_key}

Get statistical data for a dataflow and data key

GET

/dataflow/ABS

List all available dataflows

GET

/dataflow/ABS/{dataflow_id}

Get dataflow details

GET

/datastructure/ABS/{structure_id}

Get a data structure definition

GET

/codelist/ABS/{codelist_id}

Get codelist values

GET

/conceptscheme/ABS/{scheme_id}

Get a concept scheme

Why Jentic?

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

Setup

Wiring the ABS Data API by hand means learning its SDMX-style paths, pointing at the data.api.abs.gov.au host, and shaping dataflow and data-key requests yourself. Through Jentic you install once, import the ABS Data API from the Jentic API Directory, and your agent calls it.

Permission scoping

The ABS Data API is read-only, so nothing can be mutated. You still choose which of the six operations your agent may call, and because the dataflow id sits in the URL path (/data/{dataflow_id}/{data_key}), a rule can pin the agent to a single dataflow so it reads that series and nothing else.

Credential isolation

The ABS Data API is public and needs no credential, so there is nothing to store or inject. Your agent reaches it directly through your own Jentic One instance.

Intent-based discovery

Agents search Jentic by intent such as 'list ABS dataflows' or 'get labour force statistics', and Jentic returns the matching ABS operation with its input schema so the agent calls the right endpoint without reading the SDMX reference.

FAQs

Specific to using Australian Bureau of Statistics Data API through Jentic.

Why is there no official OpenAPI spec for the ABS Data API?

The Australian Bureau of Statistics publishes the ABS 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 ABS Data API use?

None. The ABS Data API is a public service, so there is no key or token to supply. Through Jentic your agent calls it directly, and the operations it may call are governed by your own rules.

What can an agent do with the ABS Data API?

It can list the published dataflows, read the observations for a dataflow and data key, and resolve the data structures, codelists, and concept schemes that describe each series. The responses are structured so an agent can parse and act on them directly.

What are the rate limits for the ABS Data API?

Rate limits are not specified in the OpenAPI spec. Check the Australian Bureau of Statistics documentation for current limits. Through Jentic, retries are handled in the execution layer.

How many endpoints does the ABS Data API have?

The ABS Data API exposes 6 read endpoints covering dataflows, data, data structures, codelists, and concept schemes.

Can I limit what my agent is allowed to do with the ABS Data API?

Yes. Jentic One is self-hosted by you, so your own rules decide which ABS operations your agent may call. The service is read-only, so nothing can be mutated, and because the dataflow id sits in the URL path, such as /data/{dataflow_id}/{data_key}, a rule can pin the agent to a single dataflow and nothing else.

Abs Australian Bureau of Statistics Data API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness Intelligencenone6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Query Australian Bureau of Statistics statistical data, dataflows, codelists, and concept schemes. Covers 6 read operations over a public, no-auth service.

Use for: Get ABS statistics for a dataflow, List the available ABS dataflows, Show the data structure for a dataflow, Look up codelist values

Not supported: Does not handle data visualization or any write operations - use it for reading Australian Bureau of Statistics data only.

Jentic publishes the only available OpenAPI specification for Australian Bureau of Statistics Data API, keeping it validated and agent-ready. The ABS Data API serves official Australian statistics in the SDMX format: an agent can list the published dataflows, read the data for a chosen dataflow and data key, and resolve the data structures, codelists, and concept schemes that describe each series. It is a public, read-only service covering national accounts, labour, prices, and population figures.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: D+Signals: 1

48%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Australian Bureau of Statistics Data API to your agent

Capabilities

Start building with Australian Bureau of Statistics Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Abs Australian Bureau of Statistics Data API

Jentic AI Readiness Score

Australian Bureau of Statistics Data API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness