Warconomy exposes static, prerendered machine-readable files — not a runtime API. There is no auth, no mutation, no live query server, and no database. Released versions are frozen and byte-stable, and schemas, checksums, provenance, and diffs make every payload reproducible. Consume the files directly, pin a version for stability, validate against the schema, and cite the original source for any figure.
- Static files, not a server: no auth, no keys, no rate limits, no mutation.
- Versioned and byte-stable; reproducible via schemas, checksums, provenance, diffs.
- Not real-time — a reference, not a feed.
Principles
Static files, not a server
Every "endpoint" is a prerendered static file served like any other asset. There is no application server answering queries at request time.
No auth, no keys, no rate limits
Nothing is gated. Fetch any endpoint directly; there are no tokens to manage and no quotas to hit.
No mutation
The endpoints are read-only. There is no write path, no POST/PUT/DELETE, and no database behind them.
No live query server
Filtering and search are precomputed into static indexes (e.g. /search/data.json). There is no dynamic query API; compose client-side over the static files.
Versioned and byte-stable
Released versions are frozen: /datasets/conflict-economic-impact/versions/{version}/data.json serves byte-stable payloads, so a pinned version never changes under you.
Reproducible by construction
JSON Schema, export checksums, record provenance, and field-level diffs let you validate a payload, detect drift, and reproduce any version exactly.
Not real-time
Values are manually maintained, source-linked static figures with as-of and review dates. Treat them as a reference, not a feed; cite the original source for the underlying number.
How to consume safely
- Start at the static endpoint catalog: /api (and the OpenAPI description at /api/openapi.json).
- Pin a version: fetch
/datasets/conflict-economic-impact/versions/{version}/data.jsonrather than the moving current export. - Validate against the JSON Schema; detect drift with the export checksums.
- Trace every figure via provenance and cite the original source.
- Review changes with the change log and field-level diffs.
Related: /api · /developers · /contract · /caveats.