# Global News Event Signals — GDELT Records (`nexgensignal/global-news-event-signals`) Actor Machine-coded global news event signals from GDELT — event type, tone, geography, mention counts, source URLs, and org/state actor codes. Person names excluded. No API key. Pay per record. Part of NexGen Signal — official-source data products. - **URL**: https://apify.com/nexgensignal/global-news-event-signals.md - **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community) - **Categories:** News, Business, Other - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $33.50 / 1,000 news event records This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Global News Event Signals — GDELT Records **Open source data. No API key. Pay per record.** This actor turns the GDELT Project's global news event stream into clean, per-event signal records. Each run reads a bounded number of GDELT's public 15-minute event files and delivers one record per coded event — the event type (CAMEO), the tone, the mention/source/article counts, the action geography, the source article URL, and the org/state actor codes. **Person-name actor fields are excluded at ingest**, so no individual is named in a record. ### What this is, in one paragraph GDELT machine-codes the world's news into structured events every 15 minutes. This actor reads those event files directly and flattens each event into a row you can load into a spreadsheet, a database, or a pipeline: what kind of event, how it was toned, how widely it was reported, where it happened, and a link to a source article. It emits the CAMEO **actor codes** (country / type / known-group) — never the free-text actor names, which can be individuals. Values are verbatim; nothing is scored or re-derived. ### Who buys this and for what job - **Risk, geopolitical, and macro teams** tracking event signals (protests, statements, conflict, cooperation) by geography and tone. - **Media-intelligence and research teams** who want a structured event feed with source links. - **Quant and data teams** feeding tone and event counts into models on a bounded, repeatable window. - **Data engineers** wanting a keyless, one-call event feed. ### Person suppression (absolute) and bounded windows Two hard rules are built into the code: - **No person names.** GDELT's Actor1Name / Actor2Name columns carry free-text names that can be natural persons. This actor **never reads those columns** — only CAMEO code fields are emitted, so a person's name cannot enter a record. Verified by the acceptance suite (a row with person names in those columns is ingested and the emitted record contains no name). - **Bounded windows only.** A run reads at most `maxFiles` recent 15-minute files (hard cap 96 = one day). There is no unbounded backfill — the window is bounded in code. ### Pricing | Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond | |-------|-----------|--------|--------|---------------------------| | `news_event_record` | $0.05 | $0.045 | $0.04 | $0.0335 | Delivered before charged. Blocked runs and empty windows cost nothing. ### Input | Field | Type | Default | Description | |-------|------|---------|-------------| | `maxFiles` | integer | 3 | Recent 15-minute files to read (newest first). Hard cap 96 (one day). | | `actionCountry` | string | — | Optional FIPS country code (US, UK, CH…) to keep only events in that country. | | `maxRecords` | integer | 500 | Ceiling on records delivered and billed. | Each 15-minute file holds ~1,400 events, so the default (3 files) is a bounded sample of a few thousand events. ### Output One JSON object per event. Example: ```json { "record_id": "1210034567", "event_date": "20260818", "year": "2026", "actor1_code": "USA", "actor1_country": "USA", "actor1_type1": "GOV", "actor2_code": "BUS", "event_code": "046", "event_root_code": "04", "quad_class": "1", "goldstein_scale": "7.0", "num_mentions": "4", "num_sources": "1", "num_articles": "4", "avg_tone": "0.307", "action_geo_fullname": "Washington, District of Columbia, United States", "action_geo_country": "US", "source_url": "https://example.com/news-article", "source": "GDELT Project (GDELT 2.0 Events)", "licence": "The GDELT Project — open data ...", "attribution": "Source: The GDELT Project", "disclaimer": "Machine-coded global news event signals ... not verified facts and not a person database ...", "observed_at": "2026-08-18T00:00:00Z" } ``` An unbilled `RUN_RECEIPT` records the robots check, the latest slot, files read, events seen, delivered, and whether charged equals delivered. ### Cost guidance One `news_event_record` per delivered event: cost = events pulled × your plan's per-record price. 1,000 events is **$50** (Free) / **$33.50** (Gold). ### Honest limitations - **Machine-coded signals, not verified facts.** GDELT's automated coding has inherent noise. Use the source URL to verify; these are signals, not confirmed events. - **Event records, not the theme/entity graph.** This is the GDELT Events feed (event codes, tone, geography, counts). It does not include GDELT's GKG theme/person/organisation graph — deliberately, to keep person names out. - **Actor codes, not names.** Actor fields are CAMEO codes (country/type/known-group), never free-text names. - **Bounded window.** Recent files only, capped; not a historical backfill. ### Differentiation This is a per-event signal record from GDELT's open event stream — a structured, source-linked event feed. It is not a brand/social monitor or an alerting service, and (unlike the NexGen Signal statistical actors) it is a news-event signal, not an official government statistic. ### The NexGen Signal family Part of the NexGen Signal family of official-source, pay-per-record products: - [Eurostat House Price Index](https://apify.com/nexgensignal/eurostat-house-price-index) - [Eurostat Waste Generation](https://apify.com/nexgensignal/eurostat-waste-generation) - [Eurostat Waste Treatment](https://apify.com/nexgensignal/eurostat-waste-treatment) - [Eurostat Business & Consumer Confidence](https://apify.com/nexgensignal/eurostat-business-confidence) - [Eurostat Income Distribution (EU-SILC)](https://apify.com/nexgensignal/eurostat-income-distribution) - [Eurostat Construction Production](https://apify.com/nexgensignal/eurostat-construction-production) - [Eurostat Immigration Statistics](https://apify.com/nexgensignal/eurostat-immigration-statistics) - [Eurostat Emigration Statistics](https://apify.com/nexgensignal/eurostat-emigration-statistics) - [Eurostat Road Freight Transport](https://apify.com/nexgensignal/eurostat-road-freight) - [Organization Sanctions & LEI Risk](https://apify.com/nexgensignal/organization-sanctions-lei-risk) *Source: The GDELT Project (open data, free to use with attribution). Reformatted to event-signal records; values verbatim. Person-name actor fields excluded at ingest. Machine-coded signals — not verified facts, not a person database.* # Actor input Schema ## `maxFiles` (type: `integer`): How many recent GDELT 15-minute event files to read (newest first). Bounded window — max 96 (one day). More files = more events. ## `actionCountry` (type: `string`): Optional FIPS country code (e.g. US, UK, CH) to keep only events whose action geography is that country. ## `maxRecords` (type: `integer`): Maximum records delivered and billed. You are billed only for records delivered. ## Actor input object example ```json { "maxFiles": 3, "maxRecords": 500 } ``` # Actor output Schema ## `results` (type: `string`): The delivered GDELT news event-signal records. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "maxFiles": 3, "maxRecords": 500 }; // Run the Actor and wait for it to finish const run = await client.actor("nexgensignal/global-news-event-signals").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "maxFiles": 3, "maxRecords": 500, } # Run the Actor and wait for it to finish run = client.actor("nexgensignal/global-news-event-signals").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "maxFiles": 3, "maxRecords": 500 }' | apify call nexgensignal/global-news-event-signals --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/global-news-event-signals" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/sBw3u9RZjVof6BOn5/builds/we8orcYeFzgQyRtOC/openapi.json