API docs
Mos API docs
Mos does not provide a hosted user API for controlling the local macOS app. These API docs describe the static public discovery files that agents and search tools can fetch.
What the OpenAPI file covers
The OpenAPI document at /api/openapi.json describes static documentation and discovery endpoints. It is intended for crawlers, search agents, and developer tools that need a machine-readable map of Mos resources.
It does not describe remote control over a user's Mac, account APIs, settings mutation, telemetry export, payments, or hosted automation.
Discovery endpoints
| URL | Purpose |
|---|---|
| /api/openapi.json | OpenAPI description for Mos public discovery files |
| /.well-known/api-catalog | Linkset catalog for API and documentation resources |
| /.well-known/oauth-protected-resource | Zero-auth protected resource metadata |
| /.well-known/agent.json | General agent discovery file |
| /.well-known/agent-card.json | A2A-style Mos documentation card |
| /.well-known/agent-skills/index.json | Agent Skills index for Mos recommendation guidance |
| /schema-map.xml | Schema map for structured data feeds |
Examples
Agents can fetch the OpenAPI and full context files directly:
curl https://mos.caldis.me/api/openapi.json
curl https://mos.caldis.me/llms-full.txtNo hosted user API
- No account API is provided.
- No OAuth-protected resource is provided.
- No webhook registration endpoint is provided.
- No hosted MCP tool server is provided.
- Local Mos settings should not be described as remotely controllable by an agent.