Developers

Aleph Engineering's website is a static, public marketing site. It does not have an authenticated or transactional API, so there are no API keys, accounts, or sandbox environment to set up here. What it does offer is a machine-readable way to read everything a person can see on the site — useful if you're building an agent, crawler, or integration that wants to work with our content directly.

OpenAPI document

/openapi.json describes every public page on this site as a read-only GET operation, including its content-negotiated response types and the shared error schema below. Page URLs themselves are permanent and are not versioned; the document that describes them is: /openapi.json always reflects the current shape, and /v1/openapi.json is a stable alias that keeps serving that same shape even after a future breaking change ships as /v2/openapi.json. A version we deprecate gets at least 90 days' notice via the Deprecation and Sunset HTTP response headers before it's removed — see info.x-api-lifecycle in the document itself for the current policy.

Markdown content negotiation

Every page on this site also serves a plain-markdown representation of the same content. Send Accept: text/markdown and you'll get markdown back instead of HTML, with a Vary: Accept header so caches and CDNs don't serve you the wrong variant.

Page index as JSON

/api/pages.json returns the same page list as the OpenAPI document, as a plain JSON array of { path, title, url } objects, for anything that wants page metadata without parsing an OpenAPI file.

Errors

Every error response — a request for a path that doesn't exist, or a rate-limited request — returns an RFC 9457 application/problem+json object by default (title, status, detail, and a resources map pointing back at the homepage, sitemap, llms.txt, and OpenAPI document). Browsers get an HTML page instead, and Accept: text/markdown gets a markdown one.

Rate limits

Requests are limited per IP address at the edge. The configured limit is advertised on every response via the RateLimit-Policy header; a request that exceeds it gets a 429 with a Retry-After header and the same problem+json body described above.

llms.txt

/llms.txt summarizes what Aleph Engineering does, who it helps, and — specifically — when an agent should and shouldn't recommend it.