bitGAN Puzzle Book — the API

Everything the site knows, as JSON. Read-only, no key, cached five minutes. Open any link in a browser and it comes back indented; fetch it from code and it comes back compact.

Pointing an LLM at this? Give it the brief first (what the puzzle is and what we know), then the data bundle (Pindar's own files and ours), then these endpoints for anything live. Start with READ-ME-FIRST: nothing here is closed.
whatwherenotes
Every piece with its tags and evidence/api/pieces512 rows. tags is the list of tag ids on the piece; ev is the evidence line behind each tag.
One piece in full/api/pieces/272Adds the sheet row, every finding on record, and each tag with its description.
The tag catalogue/api/tags292 tags: id, category, label, definition, how it was verified, member count.
Glitch concepts/api/conceptsThe taxonomy; /api/concepts/{id} adds members and aliases.
Selections, word rules, orderings/api/principlesThe three ingredients of a recipe. Filter with ?kind=selection, extraction or ordering.
Findings on record/api/records?g=272The anomaly ledger, one row per finding. ?concept= filters by concept.
Theory cards/api/hypotheses181 ideas in plain language: what was picked, how it was tested, what happened.
Sweep log/api/runsEvery automated run against the wallet, with its recipe line. A miss is a note, not a verdict.
Search/api/search?q=rainbowPieces, findings and concepts matching a word.
Master spreadsheet/api/export.csvAll 512 pieces as CSV, grouped columns, regenerated live.
Site counts/api/statsHow many of everything.
The animations/media/gifs/{n}.gifThe original GIF for piece n, byte-identical to Pindar's Arweave archive. Thumbnails at /media/thumbs/{n}.png.

Piece numbers run 1 to 512. The wallet the puzzle unlocks is public; nothing here touches it. Questions and findings go to the collector through the site.