Since April these docs have lived at dev.torchandlily.com, and the front door of the
project — torchandlily.com — has held first a wiki and then an altar. That allocation
was backwards, and it has been swapped.
Nothing you have built needs changing. The API is at api.torchandlily.com and has
not moved, your keys are untouched, and the MCP endpoint is where it was.
Changed
- The developer portal now lives at torchandlily.com — the docs, the epistulae, the changelog, the Scriptorium and the dashboard
- The altar moves to lumen.torchandlily.com, and
its e-ink surface with it, at
lumen.torchandlily.com/e - Welcome emails and OAuth consent screens now point at the portal’s new address
Unchanged
api.torchandlily.com— the API and the MCP server. No integration is affected.- Every existing API key
dev.torchandlily.com— kept indefinitely. It redirects, permanently and page for page, so an old bookmark or a link in someone’s README lands exactly where it meant totorchandlily.com/e— redirects to the altar’s new address. If you left the e-ink page running on a reader, it will find its way
A note on the reasoning
The principle we settled on is that the thing which must be discovered gets the
discoverable name, and the thing which gets bookmarked can afford a subdomain. The
altar was always meant to be one page you leave open on a spare screen — a destination,
not a doorway. It loses nothing by living at lumen.. The API and its documentation are
what we would like a stranger to find, and they had been sitting behind a hostname that
reads like a staging server.
The altar itself is unchanged in every other respect: the same day, the same saint, the same hour of the Little Office. Only its address is new.