APIs and protocols
What exists, per project, and how it is specified. Specifications publish with their repositories; none are separately hosted yet.
Summit: an openly specified protocol
Summit is the reference implementation of the Summit Protocol. In the private tree today, the protocol is defined in versioned OpenAPI, AsyncAPI, and JSON Schema documents with test fixtures, and route coverage against the OpenAPI specification is enforced in the build. The contracts are written so that an independent implementation is possible without reading Summit's source. They publish with the repository.
Pika Suite: standard protocols first
Pika Suite's interoperability story is deliberately unoriginal: IMAP, SMTP, JMAP, CalDAV, CardDAV, WebDAV, and Exchange ActiveSync against one canonical backend, so existing clients work without a bespoke integration. First-party clients use the same backend surface. There is no supported public release yet; the protocols describe the private tree.
Fairview: an API for evidence
Fairview's API, documented in its private tree, follows its operating philosophy: inventory, snapshot, drift, and safe-sync plan surfaces described alongside the product so that automation gets the same preview-and-approve discipline as the UI.
Machine-readable project data
This portal itself serves projects.json, llms.txt, and llms-full.txt with accurate, maintained project metadata.