> ## 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. # Area activity over time > Aggregate vessel activity over an area, bucketed by hour or day — distinct vessels, total + moving positions, and average/max speed per bucket. Generalizes /transits to arbitrary geography (chokepoint, bounding box, or proximity). The "is this area's traffic anomalous vs the baseline" view. Requires a plan with Maritime intelligence access (`can_use_maritime`) — the Corporate & Supply Chain plan and above. Historical / baseline surface: reads raw AIS positions directly (not the derived rollups). Forward-accruing: positions begin at launch (June 2026) — no historical backfill. Terrestrial AIS only (no satellite). Date windows are capped at 30 days; defaults to the trailing 14 days. Bucket auto-selects hour for spans ≤2 days, otherwise day. ## OpenAPI ````yaml /api-reference/openapi-v2.json get /api/v2/maritime/activity 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/activity: get: tags: - Maritime summary: Area activity over time description: >- Aggregate vessel activity over an area, bucketed by hour or day — distinct vessels, total + moving positions, and average/max speed per bucket. Generalizes /transits to arbitrary geography (chokepoint, bounding box, or proximity). The "is this area's traffic anomalous vs the baseline" view. Requires a plan with Maritime intelligence access (`can_use_maritime`) — the Corporate & Supply Chain plan and above. Historical / baseline surface: reads raw AIS positions directly (not the derived rollups). Forward-accruing: positions begin at launch (June 2026) — no historical backfill. Terrestrial AIS only (no satellite). Date windows are capped at 30 days; defaults to the trailing 14 days. Bucket auto-selects hour for spans ≤2 days, otherwise day. operationId: list-maritime-activity-v2 parameters: - name: chokepoint in: query required: false schema: type: string enum: - hormuz - bab_el_mandeb - malacca - suez - panama - bosphorus - gibraltar - dover - kerch - taiwan - danish_straits description: >- Restrict to one chokepoint. Omit to use bbox / near / near_gem_id, or for global. - name: bbox in: query required: false schema: type: string description: >- Bounding box filter: minLon,minLat,maxLon,maxLat (lon-first axis order, e.g. 56,26,57,27). - name: near in: query required: false schema: type: string description: >- Point 'lat,lon' for a radius area; combine with radius_km (default 50 km). - name: near_gem_id in: query required: false schema: type: string description: >- GEM energy-asset gem_id center — traffic within radius_km of that LNG terminal / platform (default 25 km). The cross-source 'traffic near energy infrastructure' join. - name: radius_km in: query required: false schema: type: number description: >- Radius in km for near / near_gem_id. Default 50 (near) or 25 (near_gem_id); clamped 1–2000. - name: bucket in: query required: false schema: type: string enum: - hour - day description: Time bucket. Auto-selects hour for spans ≤2 days, otherwise day. - name: date_start in: query required: false schema: type: string description: Window start YYYY-MM-DD (≤30-day window). - name: date_end in: query required: false schema: type: string description: Window end YYYY-MM-DD. - name: days in: query required: false schema: type: integer minimum: 1 maximum: 30 description: Trailing N-day window (1–30). Defaults to 14. - name: limit in: query required: false schema: type: integer default: 200 minimum: 1 maximum: 1000 description: Buckets per page (1–1000). responses: '200': description: >- Bucketed activity, most recent first. Envelope: { success, bucket ('hour'|'day'), data, pagination, applied_filters }. Each data row: bucket (timestamp), vessels (distinct mmsi), positions (AIS message count), moving_positions (sog > 1), avg_sog, max_sog (knots). content: application/json: schema: type: object properties: success: type: boolean bucket: type: string data: type: array items: type: object properties: bucket: type: string vessels: type: integer positions: type: integer moving_positions: type: integer avg_sog: type: number max_sog: type: number pagination: type: object properties: limit: type: integer cursor: {} next_cursor: {} applied_filters: type: object properties: date_start: type: string date_end: type: string chokepoint: type: string bucket: type: string ignored: type: object properties: {} examples: example: summary: GET /api/v2/maritime/activity — example response value: success: true bucket: day data: - bucket: '2026-06-14 00:00:00' vessels: 318 positions: 24117 moving_positions: 19842 avg_sog: 8.7 max_sog: 22.4 - bucket: '2026-06-13 00:00:00' vessels: 341 positions: 26508 moving_positions: 21733 avg_sog: 9.1 max_sog: 23.8 pagination: limit: 200 cursor: null next_cursor: null applied_filters: date_start: '2026-06-01' date_end: '2026-06-14' chokepoint: hormuz bucket: day ignored: {} '400': description: Invalid parameter (e.g. INVALID_BBOX, INVALID_NEAR, INVALID_RADIUS) 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' '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_...`.' ````