Releases & samples · snapshot, sample, buyer download contract
Apex publishes versioned paid snapshots, a fixed evaluation sample, and machine-readable artifact metadata so buyers can verify release state before wiring jobs or procurement.
/sample/manifest.json. Buyer files are delivered through the authenticated portal after purchase, never as public direct file URLs.Current release
Releases ship on a rolling basis. Snapshot + API customers see live corrections through the API; snapshot-only buyers receive versioned files and accumulated correction notes through the portal.
Sample manifest
The evaluation bundle is a fixed 133-row sample. Its public machine-readable metadata is available at /sample/manifest.json.
| file | format | size | sha256 |
|---|---|---|---|
| LICENSE-NOTES.md | Licence notes | 17 KB | not published |
| manifest.json | Manifest | 6.6 KB | not published |
| schema.ts | TypeScript schema | 9.0 KB | not published |
| variants.csv | CSV | 121 KB | not published |
| variants.json | JSON | 148 KB | not published |
| variants.parquet | Parquet | 110 KB | not published |
| variants.sqlite | SQLite | 4.5 MB | not published |
Paid snapshot formats
Paid releases are published as versioned bundles for warehouse loading, BI tools, local audit work, and reproducible model runs.
- JSON snapshot
application/json
- CSV snapshot
text/csv
- SQLite snapshot
application/x-sqlite3
- Parquet snapshot
application/vnd.apache.parquet
Buyer downloads
Paid snapshot files are listed in the portal after checkout. Entitled buyers can download the current release and later versioned releases tied to their SKU.
purchase SKU -> /portal -> /portal/download -> signed versioned fileRelated contracts
- ->Changelog - Release notes and corrections.
- ->Field catalogue JSON - Machine-readable field contract.
- ->Source catalogue JSON - Machine-readable source and licence contract.
- ->Buyer portal - Entitled download surface.
Questions about historical releases or enterprise delivery? Contact data@apex-db.org.