Data files
This documentation site has no backend. The pages that look interactive - the registry browser, the retention simulator, the search - read three static JSON files committed next to the HTML. They are also handy if you want to script against the demo store. Everything is a snapshot, not a live endpoint.
The three files
| Path | Shape | Used by |
|---|---|---|
| /api/artifacts.json | store snapshot: channels, retention defaults, 38 artifacts | registry browser, simulator |
| /api/commands.json | the CLI surface: global flags, nine commands, options, exit codes | CLI reference, search |
| /api/releases.json | release history, one object per version, with per-release note pages | changelog, feed |
Artifact record
Each entry in artifacts.json is one coordinate on one channel:
{
"name": "io.byteanvil.gateway",
"version": "2.4.1",
"channel": "release",
"digest": "sha256:9f2c4e71b0a8c35d…",
"size": 18446120,
"created_at": "2026-10-06T08:41:17Z",
"promoted_at": "2026-10-06T10:02:51Z",
"pinned": false,
"builder": "ci-node-3",
"commit": "a4c19e0",
"key": "7c1d9a"
}
Sizes are bytes, times are UTC with a trailing Z, digests are lowercase hex. A promoted_at of null means the artifact never left the channel it was pushed on.
Release feed
There is also an Atom feed at /feed.xml, regenerated from releases.json. Point a reader at it to get the same entries you see on the changelog.