Skip to main content
The Facilities API is a single directory of real-world physical assets — power plants, mines, pipelines, LNG terminals, ports, and AI data centers — projected from three source silos and unified on a stable facility_id: Every facility carries its owners as spine entity_ids, so a plant / terminal / field / data center joins the live Events / Stories / Entities graph — from a facility you can pivot to its operator’s entity page, or from an entity to every facility it owns. This is the join surface the physical-risk, asset-adjacent-threat, and supply-chain-disruption workflows are built on (“what exists near this event, and who operates it”).
The Facilities endpoints are plan-gated — they require the can_use_facilities entitlement, included on the Analyst plan and up. Plans below Analyst receive a clean 403 PLAN_REQUIRED.
Directory-only in v1 (list + single-facility detail + owner→portfolio). The facility × event fusion (facilities/{id}/events) is a separate stream. Facilities are rebuilt whenever a source silo reloads; owners are resolved into the same entity spine used across the rest of the API. GEM data is CC-BY 4.0 (Global Energy Monitor); ports are the public NGA World Port Index; data centers are Epoch AI (CC-BY 4.0).

Taxonomy — the type & class enums

Facilities are filtered by a leaf type or a coarse class. Both are validated enums: an unknown value returns 400 INVALID_ENUM listing the accepted set. class (coarse grouping): Pass one or more leaf types as a comma-separated type list, or a single class to grab every leaf type in that class.

Endpoints

Both endpoints require Authorization: Bearer gdelt_sk_... and return a JSON body with success: true. Non-entitled plans receive 403 PLAN_REQUIRED.

Search Facilities

GET /api/v2/facilities — search the directory, returning facility cards (identity, type/class, source silo, country + coordinates, owners with spine entity_ids, status, capacity, and follow-on URLs). Paginated with limit (max 100) + cursor.

Get Facility

GET /api/v2/facilities/{facility_id} — the full record for one facility by its stable f_ id, plus source attributes and reversible cross-silo merge_history.
The same three tools are available on the MCP server as the facilities category (facilities_search, facilities_get, facilities_by_owner) — see MCP → GDELT Cloud tools. MCP inherits the same can_use_facilities gate.