GDELT Cloud Docs — Global Event Data API & MCP

The whole published surface — 79 operations across 19 domains — so you can see what exists before deciding what to call. Each row links to its full request and response schema in the API reference. This page is generated from the same OpenAPI document the API reference renders, so it cannot list an operation that does not exist or omit one that does.

AI Compute

Operation	What it returns	Plan flag
`GET /api/v2/epoch/chip-sales`	AI chip sales	—
`GET /api/v2/epoch/companies`	AI companies	—
`GET /api/v2/epoch/data-centers`	AI data centers	—
`GET /api/v2/epoch/hardware`	ML hardware catalog	—
`GET /api/v2/epoch/models`	AI models catalog	—

Atlas Intelligence

Operation	What it returns	Plan flag
`GET /api/v2/intelligence/coverage`	Atlas coverage — where the index can and cannot be read	—
`GET /api/v2/intelligence/gpr`	Atlas GPR — geopolitical risk vs a place’s own normal	`can_use_intelligence`
`GET /api/v2/intelligence/posture`	Atlas Posture — a place’s structural + dynamic risk posture	—

Briefs

Operation	What it returns	Plan flag
`POST /api/v2/briefs`	Create Brief	—
`GET /api/v2/briefs`	List Briefs	—
`GET /api/v2/briefs/{id}`	Fetch Brief	—

China

Operation	What it returns	Plan flag
`GET /api/v2/china/projects`	China dev-finance projects	—
`GET /api/v2/china/projects/summary`	China dev-finance rollup	—

Energy

Operation	What it returns	Plan flag
`GET /api/v2/energy/assets`	Search Energy Assets	—
`GET /api/v2/energy/assets/{tracker}/{gem_id}`	Get Energy Asset	—
`GET /api/v2/energy/assets/map`	Map Energy Assets	—
`GET /api/v2/energy/assets/summary`	Summarize Energy Assets	—
`GET /api/v2/energy/owners`	Search Energy Owners	—
`GET /api/v2/energy/owners/{entity_id}`	Get Energy Owner	—

Entities

Operation	What it returns	Plan flag
`GET /api/v2/entities`	Search Entities	—
`GET /api/v2/entities/{entity_id}`	Get Entity	—
`GET /api/v2/entities/{entity_id}/hierarchy`	Corporate hierarchy for a resolved entity	—
`GET /api/v2/entities/{entity_id}/tone`	Entity tone (by entity)	—

Events

Operation	What it returns	Plan flag
`GET /api/v2/events`	Search Events	—
`GET /api/v2/events/{event_id}`	Get Event	—
`GET /api/v2/events/{event_id}/stories`	Get Event Stories	—
`GET /api/v2/events/summary`	Summarize Events	—

Facilities

Operation	What it returns	Plan flag
`GET /api/v2/facilities`	Search Facilities	`can_use_facilities`
`GET /api/v2/facilities/{facility_id}`	Get Facility	`can_use_facilities`
`GET /api/v2/facilities/{facility_id}/context`	Facility context	`can_use_facilities`
`GET /api/v2/facilities/{facility_id}/units`	List Facility registry units	`can_use_facilities`

Filings

Operation	What it returns	Plan flag
`GET /api/v2/filings`	List SEC filings	—
`GET /api/v2/filings/{cik}`	Filer profile	—
`GET /api/v2/filings/{cik}/facts`	Filer XBRL facts	—
`GET /api/v2/filings/{cik}/relations`	Filer relations (LLM)	—
`GET /api/v2/filings/events`	Material events (8-K)	—
`GET /api/v2/filings/resolve`	Resolve to CIK	`can_use_filings`
`GET /api/v2/filings/summary`	Summarize filings	—

Geography

Operation	What it returns	Plan flag
`GET /api/v2/geo/admin1`	List Admin1 Values	—

Government

Operation	What it returns	Plan flag
`GET /api/v2/gov/awards`	Federal Awards (USAspending)	—
`GET /api/v2/gov/fara`	Foreign Agents (FARA)	—

Macro Finance

Operation	What it returns	Plan flag
`GET /api/v2/macro/observations`	List FRED observations	—
`GET /api/v2/macro/releases`	List FRED releases	—
`GET /api/v2/macro/series`	List FRED series	—
`GET /api/v2/macro/series/{series_id}`	Get FRED series detail	—

Maritime

Operation	What it returns	Plan flag
`GET /api/v2/maritime/activity`	Area activity over time	—
`GET /api/v2/maritime/carriers/{imo}`	Vessel by IMO	—
`GET /api/v2/maritime/chokepoint-watch`	Chokepoint risk watch	—
`GET /api/v2/maritime/density`	Spatial density grid	—
`GET /api/v2/maritime/dwell`	Chokepoint dwell episodes	—
`GET /api/v2/maritime/gaps`	AIS-dark gaps	—
`GET /api/v2/maritime/port-pulse`	Port disruption pulse	—
`GET /api/v2/maritime/ports`	Ports reference	—
`GET /api/v2/maritime/tracks`	Raw position points in an area	—
`GET /api/v2/maritime/transits`	Chokepoint transit activity	—
`GET /api/v2/maritime/vessels`	Current vessels (last-known)	—
`GET /api/v2/maritime/vessels/{imo}/track`	One vessel’s track over time	—

Media Intelligence

Operation	What it returns	Plan flag
`GET /api/v2/entity-tone`	Entity tone	—
`GET /api/v2/entity-tone/runs`	List tone runs	—
`POST /api/v2/entity-tone/runs`	Trigger a tone run	—
`GET /api/v2/entity-tone/runs/{run_id}`	Tone run status	—
`GET /api/v2/share-of-voice`	Share of Voice	`can_use_share_of_voice`

Operation	What it returns	Plan flag
`GET /api/v2/meta/endpoints`	Endpoint contracts, machine-readable	—
`GET /api/v2/meta/enums`	Value vocabularies, machine-readable	—
`GET /api/v2/meta/query-units`	What a call costs, and what your plan allows	—

Reference Data

Operation	What it returns	Plan flag
`GET /api/v2/gleif/entities`	GLEIF legal entities (Open Feed)	—
`GET /api/v2/gleif/entities/{lei}`	One GLEIF entity, with its relationships and ISINs	—
`GET /api/v2/gleif/isin`	LEI ↔ ISIN mappings	—
`GET /api/v2/gleif/relationships`	GLEIF Level-2 relationships	—

Screening and Reference

Operation	What it returns	Plan flag
`GET /api/v2/exposure`	Ownership-chain exposure	`can_use_exposure`
`GET /api/v2/lists`	List catalog	—
`GET /api/v2/lists/changes`	List change feed	—
`GET /api/v2/lists/entries`	Search list entries	—
`GET /api/v2/screening/match`	Screen a counterparty	`can_use_screening`

Stories

Operation	What it returns	Plan flag
`GET /api/v2/stories`	Search Stories	—
`GET /api/v2/stories/{story_id}`	Get Story	—
`GET /api/v2/stories/{story_id}/articles`	Get Story Articles	—
`GET /api/v2/stories/summary`	Summarize Stories	—

Unified Search

Operation	What it returns	Plan flag
`GET /api/v2/search`	Unified cross-source entity search	—

Summary endpoints take fewer parameters

Count before you list — a /summary endpoint takes almost the same filters as the list endpoint beside it, but not all of them. The ones below are the exceptions. Some are reported back under applied_filters.ignored, and strict descriptor-backed endpoints refuse undeclared parameters with 400 UNKNOWN_PARAM. Treat either result as a failed comparison, not as a count of the filtered list. Only compare successful responses after confirming applied_filters.ignored is empty on both.

Summary endpoint	Accepted by the list endpoint, not by this one
`/api/v2/energy/assets/summary`	`search`
`/api/v2/events/summary`	`collapse_duplicates`, `include_total`, `lat`, `lng`, `lon`, `near`, `radius_km`, `search`
`/api/v2/filings/summary`	`cik`, `search`
`/api/v2/stories/summary`	`collapse_duplicates`, `event_family`, `related`, `search`

Which parameters does each one take?

See Parameter reference — the shared parameter groups first, then a per-endpoint table. Values for every filter are in Value reference.

How to read this

The surface

Vocabulary

Metrics

Stories

Event codes

CAMEO Political codes

CAMEO+ domain codes

Endpoint index

AI Compute

Atlas Intelligence

Briefs

China

Energy

Entities

Events

Facilities

Filings

Geography

Government

Macro Finance

Maritime

Media Intelligence

Meta

Reference Data

Screening and Reference

Stories

Unified Search

Summary endpoints take fewer parameters

Which parameters does each one take?

​AI Compute

​Atlas Intelligence

​Briefs

​China

​Energy

​Entities

​Events

​Facilities

​Filings

​Geography

​Government

​Macro Finance

​Maritime

​Media Intelligence

​Meta

​Reference Data

​Screening and Reference

​Stories

​Unified Search

​Summary endpoints take fewer parameters

​Which parameters does each one take?

AI Compute

Atlas Intelligence

Briefs

China

Energy

Entities

Events

Facilities

Filings

Geography

Government

Macro Finance

Maritime

Media Intelligence

Meta

Reference Data

Screening and Reference

Stories

Unified Search

Summary endpoints take fewer parameters

Which parameters does each one take?