GDELT CloudGDELT Cloud
SOLUTIONS / Apps & AI agents
Software agenciesAI applicationsContent automation

Give your app a working view of the world.

Start with structured Events, connect a company to its filings, and hand your application records it can use. The same data is available through REST and MCP.

See the workflow Estimate your workload →
Real API responses Source evidence included Start in Explore
Conceptual illustration connecting an airport, city, data center and energy infrastructure at dusk
Connected-world illustration · the records and metrics below are captured API data.
SAVED API EXAMPLE
Captured 2026-09-25 · 2026-09-18 — 2026-09-24

What can my application do with this company’s developments?

GET /api/v2/events
limit 3sort significanceentity e_2af946de69c91484search NVIDIAsearch_mode lexical

Retrieve a focused feed for a known company. 3 records in this saved page.

01 / EVENT

AWS commits to more than 3 million Nvidia GPUs by 2029

Occurrence date inferred from publication. Verify the original reporting before treating it as the date the event happened.

On 2026-09-21, AWS reportedly committed to purchase 2 million additional Nvidia GPUs, adding to more than 1 million committed in March 2026. The combined total exceeds 3 million chips due before 2029, while Nvidia deliveries reportedly begin in the current quarter. Neither company disclosed the deal's cost or the precise definition of a GPU in the commitment.

Location
Seattle, United Statesnearby area
Classification
Capital Allocation Event
Significance
0.66 model score · 0–1
Confidence
0.87 coding confidence · 0–1
Articles
1
Inspect the reportingtechradar.com ↗
02 / EVENT

Nvidia reaches $1 trillion market valuation

Occurrence date inferred from publication. Verify the original reporting before treating it as the date the event happened.

On 2026-09-21, Nvidia reportedly reached a market valuation of $1 trillion. The title-only report identifies this as a major valuation milestone but provides no details on the trading move, operational drivers, or broader market effects.

Location
Santa Clara, United Statesnearby area
Classification
Capital Allocation Event
Significance
0.53 model score · 0–1
Confidence
0.42 coding confidence · 0–1
Articles
1
Inspect the reportingberlingske.dk ↗
03 / EVENT

Zayo secures Corning fiber for AI network expansion

Occurrence date inferred from publication. Verify the original reporting before treating it as the date the event happened.

On 2026-09-18, Zayo announced an expanded strategic supply agreement with Corning to secure fiber optic cable for its planned network expansion. Zayo plans to add 15,000 route miles by 2030, including more than 8,000 long-haul miles in collaboration with Nvidia. The agreement responds to reported tightening fiber supply driven by broadband, data-center and AI demand.

Location
United Statescountry or region
Classification
Communications Infrastructure
Significance
0.45 model score · 0–1
Confidence
0.78 coding confidence · 0–1
Articles
1
Inspect the reportingrcrwireless.com ↗
Use This Data Exact request · JSON · curl · Python · TypeScript

Captured 2026-09-25. These are the exact saved dates and identifiers. Running this request again can return changed results.

GET https://gdeltcloud.com/api/v2/events?date_start=2026-09-18&date_end=2026-09-24&limit=3&include_images=false&include_entity_images=false&sort=significance&entity=e_2af946de69c91484&search=NVIDIA&search_mode=lexical
: "${GDELT_CLOUD_API_KEY:?Set GDELT_CLOUD_API_KEY}"
curl --fail-with-body --max-time 60 --get 'https://gdeltcloud.com/api/v2/events' \
  --header "Authorization: Bearer $GDELT_CLOUD_API_KEY" \
  --header 'Accept: application/json' \
  --data-urlencode 'date_start=2026-09-18' \
  --data-urlencode 'date_end=2026-09-24' \
  --data-urlencode 'limit=3' \
  --data-urlencode 'include_images=false' \
  --data-urlencode 'include_entity_images=false' \
  --data-urlencode 'sort=significance' \
  --data-urlencode 'entity=e_2af946de69c91484' \
  --data-urlencode 'search=NVIDIA' \
  --data-urlencode 'search_mode=lexical'

Pagination: this is one saved page. Follow the response’s pagination contract to retrieve additional pages; each request uses additional QU. Treat incomplete coverage as incomplete, including an empty result.

All requested dates were served in this capture. 7 served dates. Recorded examples are historical; current results may differ.

INSIDE THE EVENT RECORD

What happened. Who’s involved.
Why it deserves attention.

GDELT Cloud adds structured classification, actor roles, geographic precision and explainable Event metrics to the raw article stream. Here is what the API returned for one Event in this workflow.

CAMEOPLUS · CO05

AWS commits to more than 3 million Nvidia GPUs by 2029

Capital Allocation Event · 2026-09-21

Reported location
Seattle, United Statesnearby area
Occurrence date basis
publication day inference
Evidence returned
1 articles · 1 evidence sources · 1 supporting StoriesArticle volume is not a count of independent corroborations.
source actorAWS
target actorNvidia
LINKED IDENTITIESNVIDIA ↗e_2af946de69c91484AWS ↗e_c11713b5753cb9c4
SCORES FROM THIS RESPONSE
Significance0.66 / 1

Prioritize within the returned feed.

Coding confidence0.87 / 1

How confidently the reporting was coded.

Magnitude7.0 / 10

Intensity on the event’s domain scale.

Systemic importance0.80 / 1

How much the wider system depends on the node.

Propagation potential0.60 / 1

Potential for effects to travel beyond the event.

Market sensitivity0.60 / 1

Exposure of traded claims to the development.

Model judgments for prioritization, not measured losses or calibrated probabilities. Compare magnitude within its event domain. Missing scores stay unknown.

Open the reasoning returned with these scores

Magnitude

AWS committed to more than 3 million Nvidia GPUs due before 2029, a major strategic AI infrastructure deployment.

Systemic importance · interconnectedness

The chips serve hyperscale cloud and AI data-center operations, although the article does not quantify downstream customers.

Propagation · transmission channel

The commitment directly links AWS cloud infrastructure demand with Nvidia's GPU production and deliveries.

Market sensitivity · economic effect

A major purchase commitment has been made, but delivery and total deal cost remain unspecified and much of the deployment is future-dated.

Captured 2026-09-25 · Metric version v2-2026-07-24 · First Event in Start simpleMetric definitions and limitations ↗

THREE STEPS, A WORKING WORKFLOW

Choose your scope.
Inspect the evidence. Use the records.

01

Retrieve a focused feed for a known company.

Dates, topics, places and classification are explicit request parameters.

02

Inspect the event type, identity and linked evidence.

Keep original sources, model scores and coverage beside the result.

03

Add filing context and copy the integration.

Copy a request into your application. Start with one bounded page.

DATA BEHIND THIS WORKFLOW

Connect the company to SEC EDGAR

GDELT Cloud codes Events and clusters Stories from the raw GDELT article stream. These structured records are GDELT Cloud outputs; GDELT’s own coded Events, themes and tone are not inputs.

Follow a canonical company identity into its SEC filer record and disclosed relationships. Keep returned filing dates and accession identifiers alongside reporting dates. Relationship rows do not always return a filing date.

The Event query and SEC filer share the same resolved company identity. Filing evidence has its own reporting date.

Select “Add more context” in the saved demo to inspect the additional records ↑

SHAPED BY CUSTOMER USAGE

Paying agency and content-technology accounts repeatedly retrieve Stories by topic and country; another uses both Events and Stories. This example adapts that retrieval pattern into a company-focused application.

Based on observed recurring requests from paying accounts. This adapted demo is illustrative; the additional dataset combination is a possibility you can build, not a claim about the customer’s deployment.

WORK WITH WHAT YOU HAVE

Fill a gap.
Or build your first version.

Alongside your existing workflow

Give an existing agent or application structured external context alongside your own retrieval and business data.

From a blank page

Begin with one working company watch, then adapt the request and response schema for a client application.

YOUR WORKLOAD, MADE EXPLICIT

Small start.
Room to build.

Model the whole retrieval workflow before you integrate it. Adjust polling, pagination, detail calls and additional context.

This estimate uses 30 days. Detail calls are 1 QU each; saved enrichment is charged once per run. Retries default to zero. It does not include other account usage.

420 QU / month420 requests including the retry allowance
Builder · $59/month

Lowest current public monthly plan covering these QU and required REST capabilities. 1,500 QU included.

Annual option: $590 billed yearly.

Hosted Monitors are separate: 3 capacity · daily minimum cadence. This calculator models API polling.

Compare plans and standard trial eligibility →

REST + MCP

The demo is the beginning.
The API is the product.

Copy the captured request in curl, Python or TypeScript above. For an AI workflow, connect the GDELT Cloud MCP server and ask your client to use the same supported filters. Inspect the tool’s current schema before calling it; REST query names are not assumed to be MCP argument names.

Read the API and MCP documentation

GO DEEPER INTO THE DATA

Know what is behind each record.

SEC EDGAR FRED economic series

Also explore GLEIF identity records, NGA World Port Index, Epoch AI and World Bank data in the data/API menu.

MORE WAYS TO BUILD

Supply chain & logisticsSupply-chain software ↗News & content productsNews applications ↗Country & location researchRegional risk advisory ↗