Consumer contract

Data contract FAQ

Frequently asked questions about consuming Warconomy's data contract: is there an API, how do I pin a version, how often does it update, can I cite it, what's the license, and how is integrity verified. Static, source-linked, partial coverage, not real-time.

static reference · data June 5, 2026

Warconomy's data contract is a set of static, source-linked files with no runtime API. Pin a frozen version for reproducibility, validate against the published schemas, verify integrity with the checksums, and cite the linked source for any live figure. It is additive and backward-compatible, manually maintained, partial in coverage, and not real-time.

  • 8 questions answered.
  • No API, no auth — static files only.
  • All surfaces: /contract · compatibility: /contract/compatibility.

Questions

Is there a runtime API?
No. Every endpoint is a static, prerendered file. There is no authentication, no API key, no rate limit, and no mutation. Fetch and cache the files like any other asset.
How do I pin a version?
Use the version registry at /datasets/conflict-economic-impact/versions/data.json to choose a version, then fetch its frozen payload at /datasets/conflict-economic-impact/versions/{version}/data.json. Frozen payloads are byte-stable and never change.
How often does the data update?
It is manually maintained and refreshed by hand from cited public sources. It is not real-time. Each live value carries an as-of date and a review date so you can judge freshness.
Can I cite a figure?
Yes — cite the linked source for any live value. Do not cite the clearly-labeled sample rows; they are illustrative. Ready-made citations are at /citations.
What changed between versions?
The contract changelog at /developers/changelog lists the export fields each version added. Record counts have been stable, so versioned changes are additive shape changes, not value changes.
How is integrity verified?
Each export surface has a deterministic djb2 fingerprint and byte length, published at /datasets/conflict-economic-impact/checksums.json (also CSV and JSONL). Use them to detect drift; they are not a security guarantee against tampering.
Will fields ever be removed?
No. The contract is additive and backward-compatible under semantic versioning — fields are only added, never removed or repurposed. See /contract/compatibility.
Does it cover everything?
No. Coverage is partial and Warconomy does not claim complete coverage of any topic. It is an economic-impact reference, not legal or compliance advice.

More: consumer-contract hub · quickstart · general FAQ.

Related Warconomy pages