entity_id, an Epoch record joins the
live Events / Stories / Entities graph: an entity like NVIDIA or Anthropic surfaces the
models it developed, the hardware it makes, the data centers it owns, and its cumulative
chip sales.
The AI Compute endpoints are generally available and plan-gated — they require the
can_use_epoch_ai entitlement, carried by the Corporate & Supply Chain and Global
Intelligence plans. A key without it receives a clean 403 PLAN_REQUIRED naming the
missing entitlement, never a silently empty result. A dedicated
/ai explorer browses the same data in the web app.Epoch AI data is published under CC-BY 4.0
and sourced from epoch.ai/data. Attribute Epoch AI when you
redistribute these values. It is a data source, not a subprocessor.
Endpoints
All five endpoints return a JSONdata array (a 403 PLAN_REQUIRED for keys without can_use_epoch_ai).
Every endpoint accepts limit; the data-centers, models, and hardware endpoints also accept
offset (alias cursor) for paging. Individual filters are noted per endpoint below.
AI Data Centers
GET /api/v2/epoch/data-centers — tracked AI data centers with owner, power (MW), compute
(H100e), cost, users, and current chip types, plus a country rollup.
AI Models
GET /api/v2/epoch/models — the notable-models catalog (developer organization, domain,
task, training compute, training hardware, accessibility, open-weights, frontier flag).
AI Hardware
GET /api/v2/epoch/hardware — the ML-hardware catalog (accelerators/GPUs) with
manufacturer, type, release date, and price.
AI Companies
GET /api/v2/epoch/companies — the tracked AI labs and their latest financials
(company type, product domains, staff count, annualized revenue, valuation, total equity
funding, founding date), ordered by valuation.
AI Chip Sales
GET /api/v2/epoch/chip-sales — cumulative chip-sales estimates by designer
(latest window per manufacturer: compute in H100e, unit count, and power in MW).
This preview reads the
epoch ClickHouse schema, which is loaded offline from Epoch AI’s
published CSVs (scripts/load_epoch.py), separately from the GDELT ingest pipeline. The
tables are small and fully enumerable; owners and manufacturers are resolved into the same
entity spine used across the rest of the API, so you can pivot from a chip designer or model
developer straight to its GDELT Cloud entity page.
