Developer overview
What cadence. exposes programmatically — REST, MCP, webhooks and agents — and which one to reach for.
cadence. has four programmatic surfaces. They share one authentication model and one set of rate limits, and all of them require a paid plan.
Which surface do I want?
Read and write projects, phases, tasks, criteria and comments from your own code.
MCP serverGive Claude, Cursor or any MCP client direct, tool-level access to your workspace.
WebhooksGet pushed a signed payload when tasks, phases, projects or comments change.
AI agentsRegister an agent as a team member and assign it work like a person.
A rough rule:
- You are pulling data on a schedule, or writing from a backend → REST.
- You want an AI assistant to operate cadence. conversationally → MCP.
- You need to react to change without polling → webhooks.
- You want work executed autonomously when it is assigned → agents.
Base URL and versioning
https://cadence.alen.world/api/v1The version lives in the path. Breaking changes will ship as a new version rather than mutating v1 under you.
The MCP server is separate, at https://cadence.alen.world/api/mcp.
Authentication in one line
Every request carries an API key:
curl https://cadence.alen.world/api/v1/projects \
-H "Authorization: Bearer cad_live_..."Keys are created in Integrations and are scoped to one team. See authentication.
Health check
One endpoint needs no authentication, for uptime monitoring:
/api/v1/healthno auth{ "data": { "status": "ok", "version": "v1", "timestamp": "2026-08-19T09:02:11.482Z" } }Everything is team-scoped
A key belongs to a team, and every endpoint filters by that team. There is no request in the API that can read or write another workspace's data, and no parameter to try. This is enforced server-side on each query, not by convention.
Where to go next
Start with authentication, then REST conventions before the endpoint reference.