> ## 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. # Vessel by IMO > One vessel by IMO number: identity, last-known position, and the matched Global Energy Monitor LNG carrier (when one exists). Position is LAST-KNOWN ONLY — no raw track. Returns 404 when no vessel identity exists for the IMO. Requires a plan with Maritime intelligence access (`can_use_maritime`) — the Corporate & Supply Chain plan and above. Forward-accruing: position history begins at launch (June 2026). Terrestrial AIS only (no satellite). ## OpenAPI ````yaml /api-reference/openapi-v2.json get /api/v2/maritime/carriers/{imo} 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/maritime/carriers/{imo}: get: tags: - Maritime summary: Vessel by IMO description: >- One vessel by IMO number: identity, last-known position, and the matched Global Energy Monitor LNG carrier (when one exists). Position is LAST-KNOWN ONLY — no raw track. Returns 404 when no vessel identity exists for the IMO. Requires a plan with Maritime intelligence access (`can_use_maritime`) — the Corporate & Supply Chain plan and above. Forward-accruing: position history begins at launch (June 2026). Terrestrial AIS only (no satellite). operationId: get-maritime-carrier-v2 parameters: - name: imo in: path required: true schema: type: string description: IMO number of the vessel (e.g. 9006681). responses: '200': description: >- Vessel detail. `identity` carries imo, mmsi, name, ship_type, ship_type_code, call_sign, flag (ISO-3), length_m, width_m, draught_m, gem_id. `last_position` is the last-known { lat, lon, chokepoint, last_time, sog } or null. `gem_carrier` is the matched Global Energy Monitor LNG carrier { gem_id, name, imo_number } or null. Envelope: { success, imo, identity, last_position, gem_carrier }. content: application/json: schema: type: object properties: success: type: boolean imo: type: string identity: type: object properties: imo: type: string mmsi: type: integer name: type: string ship_type: type: string ship_type_code: type: integer call_sign: type: string flag: type: string length_m: type: integer width_m: type: integer draught_m: type: number gem_id: type: string last_position: type: object properties: lat: type: number lon: type: number chokepoint: type: string last_time: type: string sog: type: number gem_carrier: type: object properties: gem_id: type: string name: type: string imo_number: type: string examples: example: summary: GET /api/v2/maritime/carriers/{imo} — example response value: success: true imo: '9006681' identity: imo: '9006681' mmsi: 636019825 name: AL GHARRAFA ship_type: LNG Tanker ship_type_code: 80 call_sign: A8XY9 flag: LBR length_m: 315 width_m: 50 draught_m: 12.4 gem_id: G100000110234 last_position: lat: 26.5731 lon: 56.2489 chokepoint: hormuz last_time: '2026-06-14 08:42:11' sog: 12.7 gem_carrier: gem_id: G100000110234 name: Al Gharrafa imo_number: '9006681.0' '400': description: Invalid IMO (INVALID_IMO) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing/invalid API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: >- Plan required (PLAN_REQUIRED) — the caller's plan does not carry the required source entitlement. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Vessel not found (NOT_FOUND) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - ApiKeyAuth: [] components: schemas: 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 securitySchemes: ApiKeyAuth: type: http scheme: bearer bearerFormat: gdelt_sk_... description: 'GDELT Cloud API key. Send as `Authorization: Bearer gdelt_sk_...`.' ````