Dak.dev Developer Portal
Use dak.dev's documented HTTP and Model Context Protocol (MCP) surfaces to connect agents with iCloud, feeds, and workflow tools. This page is the stable starting point for people and agents: it links to the API specification, service catalog, authentication guide, and MCP server metadata.
Quickstart
- Read the authentication guide to choose the correct bearer-token flow.
- Inspect the OpenAPI 3.1 document for endpoint, request, and response details.
- Connect an MCP client to the documented Streamable HTTP transport and authenticate requests with its bearer token.
Authentication and sandboxing
Dak.dev does not issue a shared API key. MCP integrations use scoped bearer tokens obtained through the self-service connection flow, so an agent only receives access to the account it is authorized to use. Sign in or create an account at /login before connecting iCloud. Use a non-production iCloud account when exploring an integration: connected data and actions always belong to that account, which provides a practical sandbox for development and testing.
Developer resources
- Developer portal
Quickstart, authentication, API conventions, and sandbox guidance.
- OpenAPI document
Machine-readable OpenAPI 3.1 description of public HTTP and MCP endpoints.
- API catalog
RFC 9727 linkset for discovering each public service.
- Authentication guide
Bearer-token and OAuth discovery instructions for agent integrations.
- MCP server card
Machine-readable Model Context Protocol server metadata.
Versioning and support
The public contract is described by the versioned OpenAPI document. Agents should pin their integration to documented operations and inspect the specification before deploying changes. Questions about a proposed integration, an access issue, or a missing capability can be sent to hey@dak.dev.