Warconomy ships a typed, versioned, reproducible contract around its dataset export. Fetch the prerendered files directly — there is no runtime API, no authentication, and no SDK to install. Pin a version, validate against the JSON Schemas or the TypeScript types, verify integrity with the published checksums, and read the contract changelog to see exactly which fields each version added. Every figure stays source-linked; clearly-labeled sample rows must never be cited as current data.
- Current export version: v1.187.0 — additive, backward-compatible.
- No runtime API · no auth · no SDK — static files only.
- Partial coverage, not real-time; values are manually maintained.
Get the data
The full export plus its machine-readable shape.
- Full dataset (JSON): /datasets/conflict-economic-impact/data.json
- Data package manifest: /datasets/conflict-economic-impact/package.json
- Static endpoint catalog: /api/data.json
- OpenAPI 3.1 contract: /api/openapi.json
Types & schemas
Typed consumption and per-surface validation.
- TypeScript types: /developers/types
- Type declarations (.d.ts): /developers/types/warconomy-types.d.ts
- JSON Schema (dataset): /datasets/conflict-economic-impact/schema.json
- Surface JSON Schemas: /datasets/conflict-economic-impact/schema-report
Validate & verify
Fixtures, a step-by-step guide, and integrity fingerprints.
- Contract fixtures: /developers/fixtures
- Validation guide: /developers/validation
- Export checksums: /datasets/conflict-economic-impact/checksums.json
Versioning & history
What changed, when, and how to pin a version.
- Contract changelog: /developers/changelog
- Version registry: /datasets/conflict-economic-impact/versions
- Record history index: /records
- Record provenance: /datasets/conflict-economic-impact/provenance.json
Guides
How to consume the contract as a developer or researcher.
- Developer guide: /developers
- Route catalog: /routes
- Data dictionary: /data-dictionary
- Citations: /citations