⌘ Data · API & bundle
Use the corpus
The workshop is also data. The same entries the pages render are available read-only over an API — a web address other programs can fetch, with no key or account — and as one JSON data file, so you can build a tool that does not live in this browser.
110 entries across 9 sections, free to reuse and adapt with attribution. The API cannot change the corpus, and any browser can read it. It runs on this site, so there is no second service to deploy.
Endpoints
| Endpoint | Returns |
|---|---|
/api/technomancy | The index: counts, sections, endpoints. |
/api/technomancy/bundle | The whole workshop in one JSON file, including the table of links between entries. |
/api/technomancy/collections | The sections with their counts and API links. |
/api/technomancy/search?q=sigil | Name and summary search, up to 100 results. |
/api/technomancy/language | The compact 292-term Prompt Foundry lexicon. |
/api/technomancy/instruments | One section, all entries. |
/api/technomancy/entry/mercury_inbox_servitor | Every section that holds the id. |
Fetch it
// The bundle
const corpus = await fetch('/api/technomancy/bundle').then((r) => r.json());
console.log(corpus.counts);
// One section
const instruments = await fetch('/api/technomancy/instruments').then((r) => r.json());
// One entry
const entry = await fetch('/api/technomancy/entry/sigil_forge').then((r) => r.json()); The API is read-only, and any browser can call it. The bundle is the whole corpus in one response; use it when you want to copy the workshop into a local tool.
The sections
Licence and shape
The corpus is free to reuse and adapt with attribution (CC BY-SA 4.0). The
joins table in the bundle says which fields point to other entries; treat a
value as a reference only when that table says so. Each entry has an id, a
name, a summary, a kind and the practical fields for
its section.
If you build something with it, the Build guide has the anatomy of an instrument and the Instruments page has the shelf.