Overview
The reference defines each endpoint contract. These guides explain how the components work together.
They cover webhooks, public agent embeds, portable bundles, agent memory, autonomous agents, and the TypeScript SDK.
MEMORY INTELLIGENCE EXECUTION
────── ──────────── ─────────
Projects Agents Automations
Tasks Agent knowledge Webhooks out
Media Long-term memory Bundles in/out
Long-term memory 15+ frontier models Published apps
│ │ │
└────────────────────┴──────────────────────┘
│
one workspace, one token
What each guide covers
| Guide | Answers |
|---|---|
| Webhooks | How do I get told when something changes? |
| Bundles & App Kits | How do I move a whole app or workspace somewhere else? |
| Embed a Public AI Agent | How do I add an agent to my website? |
| TypeScript SDK | How do I call this from TypeScript without hand-rolling fetch? |
| SDK Cookbook | What do production integration patterns look like? |
| Long-Term Memory | Where does an agent's memory physically live, and can I edit it? |
| Autonomous Agents | How do agents run work without a human in the loop? |
Webhook events
Six event types fire outbound:
| Event | Fires when |
|---|---|
task.due |
A task reaches its due date |
task.assigned |
A task is assigned to someone |
comment.created |
A comment is added |
project.created |
A project is created |
project.assigned |
A project is assigned |
project.joined |
Someone joins a project |
Taskade signs deliveries with X-Taskade-Signature: sha256=<hex>. The signature is an HMAC-SHA256 over the raw body.
If Taskade cannot produce the signature, it skips the delivery. Taskade does not send an unsigned delivery.
The payload has no event-name envelope. Receivers must infer the event from the payload shape.Branch on required fields. Do not branch on a type discriminator that does not exist.