Skip to main content
For founders / Developers / API

Developers

Read access to public directory profiles, job listings, events, the Hub Product Codes taxonomy standard and the Data Catalog (dated observation series with a machine-readable contract per dataset), plus a write endpoint for posting job listings. Create an API key from your company workspace to get started: open-tier data endpoints answer without one.

Authentication

Every request needs an Authorization: Bearer <key> header. Create a key from your company workspace (verified representatives only): the full key is shown once, at creation.

Rate limits

120 requests per minute, per key.

Endpoints

MethodPathDescription
GET/api/v1/companiesList public directory companies
GET/api/v1/companies/:idOne company profile + public offerings
GET/api/v1/jobsList live job listings posted on the Hub (roles the Hub listed from companies' own job boards are not included)
POST/api/v1/jobsPost a job listing to your own company (ATS integration)
GET/api/v1/eventsList published events
GET/api/v1/taxonomyHub Product Codes: value-chain segments and product/service categories, plus the versioned chip lifecycle stages (?kind=lifecycle for those alone)
GET/api/v1/datasetsData Catalog listing: kind, topic, tier, computed coverage, endpoints (no key)
GET/api/v1/datasets/:slugOne dataset's observation series: JSON, or ?format=csv; ?series=, ?from=, ?to=
GET/api/v1/datasets/:slug/contractMachine-readable data contract (no key)
GET/api/v1/snapshot?date=YYYY-MM-DDPoint-in-time replay of every ledger series (no key). Add basis=recorded for what was live that day, from the append-only ledger
GET/api/v1/indicators/:slug?asOf=YYYY-MM-DDOne published indicator with its method note and history, now or as of a past day (no key)

Data Catalog tiers

Every dataset on /data is an endpoint. Open datasets, the catalog listing, every contract and the snapshot answer anonymously. Free key datasets need the bearer header above. Pro datasets are marked as such in their contract; entitlement billing is not live yet, so today a Hub API key is all the endpoint asks for.

Rows carry observedAt (the period described), recordedAt (when it entered the catalogue), sourceType and an isBackfill flag. Illustrative series are marked isSampleData: true with a sourceNote: quote them as shape, not as market prints. Agents: see /for-agents and /llms.txt.

Changes from 17 October 2026, all additive: each row also carries sourceKind (observed, research, derived, computed or estimated), confidenceTier (high, medium or low; there is no numeric score), tierBasis, estimatedBy and estimateBasis for estimates, and band with bandBasis where a range is published. sourceType keeps its earlier free-text value. The CSV adds the same columns after recorded_at. A withdrawn dataset now answers 410 with its corrections entry instead of 404, without a key. Every field is described in the contract's observationFields.

Webhooks

Verified company representatives can register endpoints for events on their own objects: new inquiry, new application, job listing expired: from the company workspace. Payloads are signed with HMAC-SHA256 in the X-Hub-Signature-256 header, and failed deliveries retry with backoff.

OpenAPI spec

/api/v1/openapi.json →

Terms of use

Only public data is ever returned: private and members-only profile fields are never exposed through this API, regardless of key. API access is subject to the platform's Terms of Service. Keys are non-transferable and scoped to the company that created them; do not share your key.