> ## Documentation Index > Fetch the complete documentation index at: https://docs.gdeltcloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Facility > Fetch a single facility by its stable `facility_id` — the full record plus source attributes and reversible cross-silo merge history. Plan-gated: requires the `can_use_facilities` entitlement (Analyst plan and up). ## OpenAPI ````yaml /api-reference/openapi-v2.json get /api/v2/facilities/{facility_id} openapi: 3.0.3 info: title: GDELT Cloud API v2 version: 2.0.0 description: >- Clean v2 REST API for generated GDELT Cloud structured Events, clustered Stories, linked Entities, summaries, admin1 discovery, significance ranking, and paginated article evidence. Event significance is a family-scoped weighted blend, renormalized so every event family spans a true 0-1: each event's raw total is divided by the maximum its own family can reach (Conflict 1.00, CAMEO+ POLITICAL 0.90, other CAMEO+ domains 0.65). All events: Goldstein severity 0.25, article evidence 0.05, confidence 0.05. Conflict only: fatalities 0.55 (log-scaled by body count) and civilian targeting 0.10. CAMEO+ only: magnitude 0.20, systemic importance 0.15, propagation potential 0.10, market sensitivity 0.10. When magnitude is unmeasured its term AND its 0.20 weight are both dropped. The four CAMEO+ metrics are rubric scores produced by published formulas - ordinal ranking signals, not measurements, probabilities, or predicted price moves. goldstein_scale is one canonical public metric, populated for Conflict Events and CAMEO+ POLITICAL Events where meaningful. Story linked_event_count is a Story-to-Event link aggregate, not a distinct Event total. servers: - url: https://gdeltcloud.com description: Production - url: http://localhost:3000 description: Local development security: - ApiKeyAuth: [] tags: - name: Events description: Coded CAMEO+ / conflict events — search, fetch, and summarize. - name: Stories description: Clustered narratives (stories) and their articles. - name: Entities description: >- People & organizations — resolve a name to an entity, then fetch its profile and tone. - name: Geography description: Admin-1 geography lookups. - name: Energy description: Global Energy Monitor assets + ownership registry. - name: Facilities description: >- Unified physical-asset directory — GEM energy assets + World Port Index ports + Epoch AI data centers on one keyed surface, resolved to spine owners. Plan-gated (Analyst plan and up). - name: Screening and Reference description: >- Restricted-party lists, screening, and ownership-chain exposure. Plan-gated (`can_use_screening` / `can_use_exposure`). - name: China description: >- China overseas development finance (AidData GCDF). Plan-gated (`can_use_china`). - name: Media Intelligence description: >- Entity tone (`can_use_tone`) and Share of Voice (`can_use_share_of_voice`) are plan-gated. Social signal remains an admin-only preview. - name: Filings description: >- SEC EDGAR filings, XBRL financials, and AI-extracted relations. Requires a plan with SEC filings access (`can_use_filings`) — the Corporate & Supply Chain plan and above. - name: Macro Finance description: >- FRED economic time series (catalog, point-in-time observations, releases). Plan-gated (`can_use_macro`). - name: Maritime description: >- AIS-derived vessel-flow signals across maritime chokepoints — chokepoint transits, last-known vessel positions, carriers, dwell, and AIS-dark gaps. Plan-gated (`can_use_maritime`). - name: Briefs description: Source-backed monitoring briefs. paths: /api/v2/facilities/{facility_id}: get: tags: - Facilities summary: Get Facility description: >- Fetch a single facility by its stable `facility_id` — the full record plus source attributes and reversible cross-silo merge history. Plan-gated: requires the `can_use_facilities` entitlement (Analyst plan and up). operationId: get-facility-v2 parameters: - name: facility_id in: path required: true schema: type: string description: The facility's stable id (f_...) from a Search Facilities card. example: f_581be6619920626d responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/FacilityDetailResponse' examples: facility: value: success: true facility: facility_id: f_581be6619920626d name: Alibaba Zhangbei facility_type: data_center facility_class: digital_infrastructure source_silo: epoch country_iso3: CHN lat: null lon: null address: >- Alibaba Zhangbei Yun Calculation Data Center, Zhangbei County, Zhangjiakou, Hebei, China status: null capacity_mw: 169 owners: - entity_id: e_a4db9cd53edee666 name: Alibaba attributes: current_power_mw: '169' current_h100e: '132895.4' chip_types: '' first_seen_date: '2026-07-09' last_seen_date: '2026-07-09' detail_url: /api/v2/facilities/f_581be6619920626d owner_portfolio_url: /api/v2/facilities?owner_entity_id=e_a4db9cd53edee666 merge_history: [] '401': description: 'API key required. Include: Authorization: Bearer gdelt_sk_...' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: error: value: error: >- API key required. Include: Authorization: Bearer gdelt_sk_... code: MISSING_API_KEY '403': description: >- The caller's plan does not carry the can_use_facilities entitlement (Analyst plan and up). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: error: value: success: false error: Your plan does not include the Facilities data source. code: PLAN_REQUIRED '404': description: No facility with that id. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: error: value: success: false error: Facility not found. code: NOT_FOUND '500': description: Failed to fetch the facility. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: error: value: success: false error: Failed to fetch the facility. code: INTERNAL_ERROR security: - ApiKeyAuth: [] components: schemas: FacilityDetailResponse: type: object properties: success: type: boolean facility: $ref: '#/components/schemas/FacilityCard' merge_history: type: array description: Reversible cross-silo merge rows (empty at launch). ErrorResponse: type: object properties: success: type: boolean enum: - false error: type: string code: type: string details: type: object description: >- Recoverable validation context when available, such as param, invalid_value, accepted_values, nearest_values, and a corrected example. additionalProperties: true FacilityCard: type: object description: >- One real-world facility in the unified directory, projected from a source silo and unified on a stable facility_id. properties: facility_id: type: string description: Stable id (f_...) — pass to Get Facility. example: f_8b0dcc8be8d5aa98 name: type: string example: AGP LNG Terminal facility_type: type: string enum: - coal_plant - oil_gas_plant - nuclear_plant - geothermal_plant - bioenergy_plant - hydropower_plant - solar_farm - wind_farm - coal_mine - oil_gas_field - iron_ore_mine - coal_terminal - lng_terminal - gas_pipeline - oil_pipeline - lng_carrier - port - steel_plant - cement_plant - chemical_plant - data_center example: lng_terminal facility_class: type: string nullable: true enum: - power - extraction - transport_logistics - ports - heavy_industry - digital_infrastructure example: transport_logistics source_silo: type: string enum: - gem - maritime_ports - epoch example: gem gem_tracker: type: string nullable: true description: The originating GEM tracker (gem silo only). example: lng_terminals country_iso3: type: string nullable: true example: USA lat: type: number nullable: true description: Null for geo-null silos (Epoch data centers in v1). lon: type: number nullable: true address: type: string nullable: true status: type: string nullable: true description: operating / construction / proposed / retired / … (varies by silo). example: proposed capacity_mw: type: number nullable: true description: Power facilities + data centers only. example: 169 owners: type: array items: $ref: '#/components/schemas/FacilityOwner' attributes: type: object description: Silo-specific extra fields (fuel, tier, capacity_unit, h100e, …). first_seen_date: type: string nullable: true last_seen_date: type: string nullable: true detail_url: type: string example: /api/v2/facilities/f_8b0dcc8be8d5aa98 owner_portfolio_url: type: string nullable: true description: >- GET /api/v2/facilities?owner_entity_id=... — the owner's full portfolio. example: /api/v2/facilities?owner_entity_id=e_a4db9cd53edee666 FacilityOwner: type: object description: >- An owner / operator of a facility. entity_id is the spine e_ id (null for owner-name-only rows, e.g. maritime ports carry no owner and some GEM owners resolve a name but not a spine id yet). properties: entity_id: type: string nullable: true description: >- Spine entity_id — join key to /api/v2/entities and the cross-source graph. example: e_a4db9cd53edee666 name: type: string nullable: true example: Alibaba securitySchemes: ApiKeyAuth: type: http scheme: bearer bearerFormat: gdelt_sk_... description: 'GDELT Cloud API key. Send as `Authorization: Bearer gdelt_sk_...`.' ````