Taskade Developer Docs

Welcome to the Taskade developer docs. Taskade turns a plain-English description of your business into a real, running app. Taskade Genesis builds the app, and the workspace underneath keeps working as its database, its agent team, and its automation engine. Taskade calls that foundation Workspace DNA: memory, intelligence, and execution. These docs show you how to reach all of it from your own code. The fastest first win is a personal access token and your first API call, which takes about two minutes.

        YOUR CODE / YOUR AGENT / YOUR AI CLIENT
                        │
     ┌──────────────────┼──────────────────┬─────────────────┐
     │                  │                  │                 │
  REST v1           Action v2         MCP servers        Webhooks
  resource-shaped   verb-shaped       tool-calling       events out
  49 paths          61 paths          hosted + local     6 event types
     │                  │                  │                 │
     └──────────────────┴────────┬─────────┴─────────────────┘
                                 │
                        ┌────────▼────────┐
                        │  WORKSPACE DNA  │
                        │                 │
                        │  Memory         │  projects, tasks, media, long-term memory
                        │  Intelligence   │  agents, knowledge, 15+ frontier models
                        │  Execution      │  automations, bundles, published apps
                        └─────────────────┘

The two layers

Think of a Taskade account the way a hosting control panel thinks about a server. There is a root layer, the workspace where members, folders, and billing live. And there is an app layer, the projects, agents, and published Taskade Genesis apps that run inside it. Every API surface below addresses one layer or the other, and most confusion dissolves once you know which one you are holding.

From zero to programmatic

The whole journey, human or agent:

1. Sign up — a free account can use the entire public API.
2. Describe your app — Taskade Genesis builds it; Preview App shows it running against your real workspace data while you iterate.
3. Publish — the app gets a live URL; the workspace underneath keeps being the database, the agent roster, and the automation engine.
4. Create a token — then everything the UI just did is addressable from code, an MCP client, or a webhook pointing back at you.

Pick a surface

Authenticate once

Every surface takes the same header. Create a personal access token at taskade.com/settings/api. The token is shown once, never expires, and you can hold five at a time.

curl "https://www.taskade.com/api/v1/me/projects" \
  -H "Authorization: Bearer tskdp_your_token_here"

The public API is not plan-gated. A Free account can mint a token and call every v1 and v2 endpoint. Two things on this surface do depend on plan: outbound webhooks need Pro or above, and MCP needs any paid plan.

How a request travels

Rate limits at a glance

Requests are rate limited to keep the service fast for everyone. Exact ceilings are not published and can change without notice, so read your budget from the response instead: every response carries x-rate-limit-limit, x-rate-limit-remaining, and x-rate-limit-reset (seconds until the window reopens). If you receive a 429, wait out x-rate-limit-reset and retry with exponential backoff. There is no Retry-After header, and retrying before the window reopens will fail again.

Two habits keep most integrations well clear of 429: batch writes where an operation accepts arrays, and prefer webhooks over tight polling loops.

Live endpoints

These pages are the crawlable reference; the running service also speaks for itself. The Swagger consoles are interactive try-it-now UIs generated by the same server that validates every request, and the raw specs behind them are what regenerate this reference.