Your product knows the places. Add what’s happening around them.
Find reported strikes, operational disruption and industrial developments. Put structured Events and source evidence beside the sites and routes your application already tracks.
Choose a region and a disruption question. 3 records in this saved page.
01 / EVENT
Skeyes strike cancels 46 flights at Charleroi airport
On 2026-09-19, Skeyes air-traffic controllers' strike canceled 46 flights at Brussels South Charleroi Airport in Belgium, including departures and matching arrivals. The walkouts were scheduled nightly from 10 p.m. to 8 a.m. through October 10, disrupting passenger air transport and potentially stranding travelers. The article does not report deliberate infrastructure sabotage.
Location
Brussels South Charleroi Airport, Belgiumexact place
Slovakia hands Ukraine its first electric locomotives
Occurrence date inferred from publication. Verify the original reporting before treating it as the date the event happened.
On 2026-09-21, Slovakia handed Ukraine its first electric locomotives at the Carpathian summit. The transfer supports Ukraine's railway capacity amid intensified Russian strikes on railway infrastructure, but the article gives no locomotive count or deployment details.
Occurrence date inferred from publication. Verify the original reporting before treating it as the date the event happened.
On 2026-09-20, additional diesel fuel was reportedly delivered to the Zaporizhzhia Nuclear Power Plant in Enerhodar, Ukraine, for reserve generators supporting the station during external power interruptions. The article gives no quantity and does not report a new outage. It also references reported strikes on fuel trucks on September 11, but that earlier incident is contextual to the current delivery update.
Location
Zaporizhzhia Nuclear Power Plant, Enerhodar, Ukraineexact place
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 · IN02
Skeyes strike cancels 46 flights at Charleroi airport
Transport Disruption · 2026-09-19
Reported location
Brussels South Charleroi Airport, Belgiumexact place
Occurrence date basis
explicit date
Evidence returned
3 articles · 1 evidence sources · 1 supporting StoriesArticle volume is not a count of independent corroborations.
source actorSkeyes
target actorBrussels South Charleroi Airport
SCORES FROM THIS RESPONSE
Significance0.42 / 1
Prioritize within the returned feed.
Coding confidence0.97 / 1
How confidently the reporting was coded.
Magnitude3.0 / 10
Intensity on the event’s domain scale.
Systemic importance0.37 / 1
How much the wider system depends on the node.
Propagation potential0.55 / 1
Potential for effects to travel beyond the event.
Market sensitivity0.38 / 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
The Skeyes strike caused 46 flight cancellations at a major Belgian airport, a significant but localized transport disruption.
Systemic importance · interconnectedness
Flight cancellations affect passengers, airlines, and connecting travel services.
Propagation · transmission channel
Operational dependency connects air traffic control directly to airport departures and arrivals, with effects on airlines and passengers.
Market sensitivity · economic effect
The disruption is in force but partial and time-bounded: 46 flights were canceled for Saturday amid nightly strike action.
MEET THE RECORDS
Four building blocks. Real examples.
A Story collects the reporting. An Event describes what happened. Entities identify who; facilities locate physical assets.
Story
Related reporting, grouped together.
Zelensky says US is preparing new investments in Ukraine's defense and energy
3 articles · linked to the Event beside it
Event
What happened, classified and located.
Zelensky says US is preparing investments in Ukraine
Make Public Statement · confidence 0.58
Entity
A person, organization or place with a reusable identity.
Nvidia
organization · 7 Stories on 2026-09-24
Facility
A physical asset with a location and registry details.
Amercoeur power station
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
Choose your scope. Inspect the evidence. Use the records.
01
Choose a region and a disruption question.
Dates, topics, places and classification are explicit request parameters.
02
Narrow the returned Events and inspect the reporting.
Keep original sources, model scores and coverage beside the result.
03
Connect the records to your own site or supplier workflow.
Copy a request into your application. Start with one bounded page.
DATA BEHIND THIS WORKFLOW
Add nearby infrastructure
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.
See registry facilities near a reported location. Keep the reported development and independently dated asset record side by side, with the relationship made explicit.
Within 50 km of the location returned for “Skeyes strike cancels 46 flights at Charleroi airport”. Proximity is context, not evidence that these assets were affected.
Put regional disruption alerts beside the sites, routes and suppliers your team already watches.
WORK WITH WHAT YOU HAVE
Fill a gap. Or build your first version.
Alongside your existing workflow
Add external reporting to the locations, suppliers and shipments already in your product. Your own records supply those business relationships.
From a blank page
Start with a regional watch in Explore, inspect the JSON, then embed a bounded Event feed in your first dashboard.
YOUR WORKLOAD, MADE EXPLICIT
Small start. Room to build.
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.
List requests
24 runs × 1 pages × 1 QU = 24 QU/day
Detail lookups
0 × 1 QU = 0 QU/day
Additional context
0 QU/day
Monthly budget
24 QU/day × 30 days
720 QU / month720 requests including the retry allowance
Builder · $59/month
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.
Estimate assumptions
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.
Describe the task. Let your agent run the workflow.
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.
