Build with your coding agent
One command wires the data and the documentation into your agent together — coded global events, deduplicated news stories, entities resolved across news, filings, sanctions lists and asset registries, and the physical assets underneath. Five workflow skills come with it.
The whole API is designed so a wrong filter is loud rather than quiet, and where it cannot be, the skills say so. For the long-form reference see the docs; for what each dataset covers and does not, see Data sources.
1. Get a key
Create one at gdeltcloud.com/api-keys. Keys look like gdelt_sk_… and are shown once. The free plan reads every dataset — paid plans buy volume and products, not access. If you only want your agent to read the reference while it writes code, skip this step and install the docs-only plugin below.
2. Connect your client
Run these two inside Claude Code. You are asked for your API key on enable, and it is stored in your keychain — not in the repo.
Documentation only, no account: /plugin install gdelt-cloud-docs@gdelt-cloud. Or wire just the docs server without the plugin:
3. Give your agent the rules
Paste this into your repo's AGENTS.md or CLAUDE.md. It is the short version of what separates a correct call from one that returns 200 with the wrong data — which is the failure mode this API actually has. The plugin ships these as skills, so you only need this if you are connecting the MCP server directly.
4. Build something
The plugin ships five skills — a Core-API primer plus war-risk underwriting, counterparty exposure, supplier disruption and country-risk series. Ask your agent for one by name, or just describe the workflow. Four complete reference implementations, each a self-contained Python project rendering a static HTML dashboard, are at github.com/gdelt-cloud/demos.