Machine-readable contracts · fields, sources, samples, discovery

Apex exposes stable JSON and text surfaces for buyers, documentation tools, and agents. These routes describe the public data contract; paid data access still runs through snapshots, REST, MCP, agent payments, or the buyer portal.

Treat these as read-only public contracts for fields, sources, releases, sample artifacts, and agent discovery. Agents can use the JSON and text routes directly instead of scraping tables or cards.

Contract index

Field catalogue

Field metadata

Schema-backed field names, groups, types, applicability, fill rates, source counts, and documentation anchors.

343 documented fields

/docs/data-dictionary/fields.json

Source catalogue

Source metadata

Schema-backed source codes, tiers, licences, commercial-use flags, source pages, docs anchors, and API route.

57 current-release sources

/sources/catalog.json

Sample manifest

Sample artifacts

Schema-backed evaluation artifact state, rows, version, release date, files, sizes, formats, checksums, schema links, and source provenance.

133 sample rows · 346 JSON fields · 346 flat columns

/sample/manifest.json

Field catalogue schema

schema/field-catalog.schema.json

Reusable JSON Schema for field groups, field metadata, examples, provenance notes, and documentation URLs.

343 field entries validate here

/schema/field-catalog.schema.json

Source catalogue schema

schema/source-catalog.schema.json

Reusable JSON Schema for source codes, jurisdictions, licences, commercial-use flags, and source catalogue links.

57 source entries validate here

/schema/source-catalog.schema.json

Sample manifest schema

Public sample metadata

Reusable JSON Schema for /sample/manifest.json.

133 sample rows validate here

/schema/public-sample-manifest.schema.json

LLM discovery

docs routes

Plain-text route index for AI systems, docs tools, and agent bootstrap flows.

compact ingestion index

/llms.txt

Agent bootstrap

Agents should start with /llms.txt, then read the field and source catalogues before composing API calls. Human reviewers should use the rendered data dictionary and source notes alongside the JSON.

contract discoverybash

curl https://apex-db.org/llms.txt
curl https://apex-db.org/docs/data-dictionary/fields.json
curl https://apex-db.org/sources/catalog.json
curl https://apex-db.org/sample/manifest.json
curl https://apex-db.org/schema/field-catalog.schema.json
curl https://apex-db.org/schema/source-catalog.schema.json
curl https://apex-db.org/schema/public-sample-manifest.schema.json
curl https://api.apex-db.org/v1/openapi.json

API alignment

The field catalogue describes response fields for /v1/apex. The source catalogue describes source codes and provenance anchors. The sample manifest describes only the public evaluation artifact, not paid buyer files.