Retrieve Stories by topic and country, inspect their sources, then connect reporting to structured Events. Build a repeatable feed without assembling the ingestion and grouping pipeline yourself.
GET /api/v2/storiesChoose a topic, country and date window. 3 records in this saved page.
Country filter: USA. May match actor origin or reported location; returned Stories can concern places outside this country.
Zelensky says US is preparing investments in Ukraine
Serhiy Koretsky discusses defense and energy with US envoy
Indiana Gov. Mike Braun announces nuclear regulatory partnership
All requested dates were served in this capture. Recorded examples are historical; current results may differ.
Try current results in Explore →INSIDE THE EVENT RECORD
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.
Make Public Statement · 2026-09-24
Prioritize within the returned feed.
How confidently the reporting was coded.
Intensity on the event’s domain scale.
How much the wider system depends on the node.
Potential for effects to travel beyond the event.
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.
The event described is Zelensky's neutral public statement about preparations for investment.
The article excerpt does not describe third-party commitments dependent on this relationship.
The statement concerns possible US investment in Ukraine, but no active transmission mechanism or binding commitment is described.
The reported investment is being prepared; no binding or realized change to a claim is described.
MEET THE RECORDS
A Story collects the reporting. An Event describes what happened. Entities identify who; facilities locate physical assets.
3 articles · linked to the Event beside it
Make Public Statement · confidence 0.58
organization · 7 Stories on 2026-09-24
oil gas plant · BEL · Global Energy Monitor
The Story and Event shown here are linked. NVIDIA and the facility are separate examples; their IDs let you connect the records returned by your own queries.
THREE STEPS, A WORKING WORKFLOW
Dates, topics, places and classification are explicit request parameters.
Keep original sources, model scores and coverage beside the result.
Copy a request into your application. Start with one bounded page.
DATA BEHIND THIS WORKFLOW
We combine the GDELT Project article stream with additional regional news sources we ingest directly. GDELT Cloud groups the reporting into Stories, classifies Events and links people, organizations and places.
Open the selected Story’s linked Events and source articles. Inspect what happened, how it is classified and which reporting supports it.
Detail is fetched using the first returned Story ID. Only Events and sources actually linked by the response are shown.
Select “Add more context” in the saved demo to inspect the additional records ↑PUT IT TO WORK
Turn a topic and a country into a repeatable feed for your app, newsletter or editorial workflow.
Redistributing GDELT Cloud-generated Events, Stories, entity matches, model extractions, scores, and other generated intelligence requires a separate written license for the agreed product and delivery scope. Source-only records and customer-authored analysis based solely on them are governed by the original source terms and carry no additional GDELT Cloud redistribution fee. Review licensing scope →
WORK WITH WHAT YOU HAVE
Feed a CMS, newsletter workflow or media-monitoring product with grouped reporting and the sources behind it.
Start with a topic feed in Explore, then copy its request into a small application or MCP workflow.
YOUR WORKLOAD, MADE EXPLICIT
Each list page, detail lookup and context request counts as an API call. Set your schedule and see exactly what it adds up to.
1 QU per list page · 1 QU per detail lookup. Your own agent’s direct MCP calls use the same rates as REST.
Lowest current public monthly plan covering these QU and required REST data access. 1,500 QU included.
Annual option: $590 billed yearly.
Hosted Monitors are separate: 3 capacity · daily minimum cadence. This calculator models API polling.
This estimate covers subscription access and API usage. It includes no separate GDELT Cloud redistribution fee for source-only records or customer-authored analysis based solely on them; upstream source terms still apply. A separate written license and any related fee may apply when redistributing GDELT Cloud-generated output. Review licensing scope →
30 days; each context workflow runs once per scheduled run, not once per result. Detail lookups are additional daily calls. Each saved list page requests up to 3 records. Retry allowance budgets additional charged calls; it is not a claim that every failed request is billed. Other account usage and Monitors are excluded.
YOUR AGENT CAN DO THIS TOO
Connect your agent to GDELT Cloud through MCP. The MCP server wraps our API endpoints, so your agent can discover the right tools, apply filters and chain the same data requests shown here.
Connect the MCP server →COMPARE YOUR OPTIONS
MORE WAYS TO BUILD