Skip to main content

​
Deployment & Configuration

Saturday runs two hostnames. This page says which is which, and lists the machine-readable endpoints an agent can fetch.

​
The two hostnames

Requesting a docs path on api.saturday.fit returns the API’s 404, not a page. GET https://api.saturday.fit/v1/ returns a discovery document whose documentation link points back here.

​
DNS

Cloudflare proxy stays disabled (DNS only, grey cloud) on the Mintlify CNAME. Mintlify terminates SSL and needs direct DNS resolution.
To verify a DNS change: dig docs.saturday.fit CNAME should answer cname.mintlify-dns.com., https://docs.saturday.fit should load this site, and Mintlify issues the certificate on its own.

​
Deploying documentation updates

Mintlify deploys from Git. Push to the docs repository’s default branch and the site rebuilds, typically in under a minute. A rebuild can also be triggered by hand from dashboard.mintlify.com on the Saturday API project.

​
Machine-readable endpoints

​
llms.txt

A short index of the API: what Saturday does, how authentication works, the core endpoints, the safety model, and a link to the full documentation. Follows the llms.txt standard. It is hand-curated in the docs repository.

​
llms-full.txt

The whole documentation corpus as one text file, for loading into an LLM context window. Mintlify generates it from the MDX sources on every build, so it is never edited or committed by hand.

​
MCP server

The Model Context Protocol endpoint. It accepts POST only; a GET answers 405. See MCP Integration for setup, and the Claude Connector for the hosted connector.

​
Site configuration

The site is configured by docs.json at the root of the docs repository, against the Mintlify docs.json schema.

​
Content structure

​
Status page

Saturday publishes system status at status.saturday.fit when it is available. That hostname does not currently resolve; until it does, reach api@saturday.fit about an incident.