GDELT Cloud Intelligence BYOK
Pricing
Pay per usage
GDELT Cloud Intelligence BYOK
Fetch GDELT Cloud Stories, Events, and Entities with your own API key and output normalized, AI-ready intelligence data for monitoring and research.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Smart Tech Resources
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
Collect and normalize GDELT Cloud Stories, Events, and Entities using the user provided API key.
Input
The input form is defined in .actor/input_schema.json. API key fields, where present, use Apify isSecret: true.
GDELT Cloud requires your own GDELT Cloud API key. This Actor does not include GDELT Cloud API credits.
Bring Your Own API Key (BYOK)
This Actor does not include third-party API credits. You must provide your own GDELT Cloud API key.
You are responsible for any third-party API usage fees. This Actor charges only for data processing, normalization, deduplication, enrichment, and Apify dataset/report generation.
Content types
Use the contentTypes input to choose the GDELT Cloud records to collect:
storiesfor clustered narrative Stories with top article evidence.eventsfor structured incident-level Events with categories, geography, metrics, and top article evidence.entitiesfor linked people and organizations connected to Stories and Events.allto collect Stories, Events, and Entities in one mixed run.
Selecting multiple content types creates a mixed output. Each dataset item includes contentType and gdeltCloudId so downstream workflows can separate records.
Output
Each dataset item follows the normalized Global News Intelligence article shape:
sourcePlatformsourceNametitleurlpublishedAtdescriptioncontentauthorimageUrlcountrylanguagecategorykeywordssentimententitiescontentTypegdeltCloudIdsignificancearticleCountraw
The key-value store record SUMMARY contains counts by source, publisher, country, language, category, sentiment, and date.
Local run
Fill the required GDELT Cloud API key in Apify before running against the provider. Do not place real API keys in source code, README examples, GitHub, public Apify examples, logs, or dataset output.
