> ## 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.

# AI chip sales

> Epoch AI chip-sales rollup (CC-BY 4.0) — cumulative installed compute by chip designer (H100-equivalent), unit counts, and power draw (MW), at the latest reported window per manufacturer. Sorted by installed compute descending. Requires a plan with AI compute & models access (`can_use_epoch_ai`) — the Corporate & Supply Chain and Global Intelligence plans.

Filter by `chip_manufacturer` (the endpoint's sole filter); any other query param is surfaced back in `applied_filters.ignored` rather than silently applied.



## OpenAPI

````yaml /api-reference/openapi-v2.json get /api/v2/epoch/chip-sales
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/epoch/chip-sales:
    get:
      tags:
        - AI Compute
      summary: AI chip sales
      description: >-
        Epoch AI chip-sales rollup (CC-BY 4.0) — cumulative installed compute by
        chip designer (H100-equivalent), unit counts, and power draw (MW), at
        the latest reported window per manufacturer. Sorted by installed compute
        descending. Requires a plan with AI compute & models access
        (`can_use_epoch_ai`) — the Corporate & Supply Chain and Global
        Intelligence plans.


        Filter by `chip_manufacturer` (the endpoint's sole filter); any other
        query param is surfaced back in `applied_filters.ignored` rather than
        silently applied.
      operationId: list-epoch-chip-sales-v2
      parameters:
        - name: chip_manufacturer
          in: query
          required: false
          schema:
            type: string
            example: Huawei
          description: >-
            Filter to one chip designer — exact, case-insensitive match. The
            designers with data are Nvidia, Google, Amazon, Huawei, AMD, and
            Cambricon; any other value returns 0 rows rather than 400. Echoed in
            applied_filters.
        - name: limit
          in: query
          required: false
          schema:
            type: integer
            minimum: 1
            maximum: 200
            default: 50
          description: Rows per page (1–200). Defaults to 50.
        - name: cursor
          in: query
          required: false
          schema:
            type: string
          description: >-
            Canonical page token — pass the `pagination.next_cursor` from the
            previous response here to fetch the next page (uniform across all
            list endpoints).
        - name: offset
          in: query
          required: false
          schema:
            type: integer
            minimum: 0
          description: >-
            Row offset for pagination. Prefer the canonical `cursor` token; both
            are supported.
      responses:
        '200':
          description: >-
            A page of chip-designer rollups. Envelope: `{ success, data,
            pagination, applied_filters }`.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        chip_manufacturer:
                          type: string
                        compute_h100e:
                          type: number
                          nullable: true
                        units:
                          type: number
                          nullable: true
                        power_mw:
                          type: number
                          nullable: true
                        as_of:
                          type: string
                          description: End date of the latest reported cumulative window.
                        entity_id:
                          type: string
                        entity_page_name:
                          type: string
                  pagination:
                    type: object
                    properties:
                      limit:
                        type: integer
                      offset:
                        type: integer
                      next_cursor:
                        type: string
                        nullable: true
                        description: >-
                          Canonical page token — pass it back as `cursor` to
                          fetch the next page (uniform across all list
                          endpoints). `null` when there are no more rows.
                      next_offset:
                        type: integer
                        nullable: true
                        deprecated: true
                        description: >-
                          Legacy — prefer `next_cursor` (still returned).
                          Numeric row offset of the next page.
                  applied_filters:
                    type: object
                    properties:
                      ignored:
                        type: object
              examples:
                example:
                  summary: GET /api/v2/epoch/chip-sales — example response
                  value:
                    success: true
                    data:
                      - chip_manufacturer: NVIDIA
                        compute_h100e: 6500000
                        units: 4100000
                        power_mw: 3100.5
                        as_of: '2025-12-31'
                        entity_id: e_9f8e7d6c5b4a3210
                        entity_page_name: Nvidia
                    pagination:
                      limit: 50
                      offset: 0
                      next_cursor: null
                      next_offset: null
                    applied_filters:
                      ignored: {}
        '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_...`.'

````