Developers

Build on Alchemyst Press.

A tiny public read API for the publication catalogue and editorial answers. No keys, no signup — fetch JSON, respect caching, and cite canonical URLs.

Quickstart

List the catalogue with GET /api/publications — it returns configured, publications, and error. Ask a question with POST /api/answer and JSON { "query": "what broke?" }. Machine-readable pages are also available via Accept: text/markdown, for example curl -H 'Accept: text/markdown' https://press.getalchemystai.com/. Full schema is at /openapi.json and the sitemap at /sitemap.xml.

Authentication and API keys

The public read endpoints require no API keys and have no signup. Rate limits are generous and responses include Cache-Control — cache GET /api/publications briefly and /openapi.json for an hour. The floating search box uses on-device inference first and falls back to POST /api/answer, which needs a server-side OpenRouter key only for operators self-hosting this site. If you run your own copy, set OPENROUTER_API_KEY and optionally STRAPI_URL plus CONTACT_EMAIL. Never expose private keys in client code.

Documentation

Start with the OpenAPI 3.1 spec — every operation has a unique operationId, a description, typed parameters, and response schemas, compatible with LLM function calling. Errors are structured JSON with error, message, and hint; unknown /api/* routes return 404 not_found as JSON, and wrong methods return 405 method_not_allowed. Agent guidance lives in /llms.txt, discovery in /sitemap.xml and /robots.txt. Editorial questions belong to Get In Touch and Contact; product docs are at getalchemystai.com/docs.

Sandbox

No sandbox keys needed — the production endpoints are safe to try read-only. Try GET /api/publications in your browser, then POST to /api/answer with a JSON query field. For markdown agents, compare HTML versus markdown negotiation on home, about, and a missing path to see the JSON and markdown error shapes. If you need a CLI, use any OpenAPI generator against /openapi.json — for example generate a shell client and script the catalogue without hand-writing integration code.

Questions about the API? Read the about page, browse publications, review privacy, or write via contact.