Fetch data.json, join each observation to its source by sourceId, validate against the published JSON Schema, pin a frozen version for reproducibility, verify integrity with the checksums file, and cite the linked source. There is no runtime API, no authentication, and nothing to install — every step is an ordinary HTTP fetch of a static file.
- Five-minute path: fetch → join → validate → pin → verify → cite.
- Static files only — no key, no rate limit, no SDK.
- Full guide: /developers · contract hub: /contract.
1 — Fetch the dataset
Pull the full export. It is a single static JSON file — no key, no rate limit.
curl -s https://warconomy.com/datasets/conflict-economic-impact/data.json -o warconomy.json2 — Join observations to sources
Every observation carries a sourceId. Join it to the sources array for the citation.
jq '.observations[] | {id, value, unit, asOf, sourceId}' warconomy.json3 — Validate against the schema
Each export surface has a JSON Schema. Validate before you trust the shape.
curl -s https://warconomy.com/datasets/conflict-economic-impact/schema.json -o schema.json
# then validate warconomy.json against schema.json with any JSON Schema validator4 — Pin a version
Pin a frozen version so your pipeline is reproducible. The registry lists every version.
curl -s https://warconomy.com/datasets/conflict-economic-impact/versions/data.json | jq '.versions[0].version'
# fetch a frozen payload: https://warconomy.com/datasets/conflict-economic-impact/versions/<version>/data.json5 — Verify integrity
The checksums file carries a deterministic fingerprint for the export and its distributions.
curl -s https://warconomy.com/datasets/conflict-economic-impact/checksums.json | jq '.entries[] | {path, fingerprint}'6 — Cite the source
Cite the linked source for any figure — never the clearly-labeled sample rows. See the citation catalog for ready-made citations.
Next
Deeper guide: /developers · all surfaces: /contract · types: /developers/types · validation: /developers/validation · citations: /citations.