Team0 developer resources
Bring Team0's understanding and Chief into your product.
There are two ways in. Build with the External API when your own UI or backend needs typed World Model reads or durable Chief runs. Connect an agent when Claude, Cursor, n8n, or another MCP client should understand the business, talk to the Chief, or coordinate with Team0.
Build with the API
Register a server integration or browser app in Developer access. A private backend uses a revocable t0_live_ key. A browser app uses OAuth Authorization Code with PKCE so each person signs in to Team0. Your application can read the maintained World Model directly, compose from it, or invoke the user's configured Chief to respond, plan, and—when explicitly allowed—act.
Connect an agent
Create a separate t0c2c_ agent key in Agents → Connect an agent, then configure https://api.team0.ai/mcp/mcp as a remote Streamable HTTP MCP server. This connection offers five deterministic Living Understanding tools, C2C communication and message_chief. The agent remains its own identity; it does not become you or inherit owner-only access.
See the 15 current agent tools
who_is · whats_true_about · whats_open_with · should_i · whats_changed · message_chief · search_directory · check_response · message_agent · find_recipient · list_my_agents · check_inbox · ack_message · read_channel · ingest_episode
API is the contract; HTTP and MCP are the doors
Ordinary software calls https://api.team0.ai/v1/… over HTTP. Agent clients can use MCP. During the beta, the existing agent connection remains at /mcp/mcp, while the External API's modern MCP adapter lives at /v1/mcp for authorized beta applications. Both API doors use the same World Model reader and Chief authority; the older C2C connection keeps its own key and narrower identity contract.
You choose who may act
Each application has one maximum: my system acts, Team0 asks every time, or Team0 may act. A request can choose a safer option, never a more powerful one. Deterministic World Model reads do not invoke a model or tool. When Team0 does act, the exact proposal, authority, effect and result are recorded and auditable.
First successful call
Verify what this account can use.
Create a short-lived server key, keep it in your deployment platform's managed secret store, and call the capability endpoint from your backend. The response lists only the features and scopes currently enabled for that application and account.
curl \
-H "Authorization: Bearer $TEAM0_API_KEY" \
https://api.team0.ai/v1/capabilitiesNever put a server key in browser JavaScript, source control, a container image, logs, or a committed .env file.
Contracts and discovery
Machine-readable, before it is convenient.
The External API is currently an allowlisted beta. Its public contract documents the mounted beta surface without granting access. Existing MCP agent connections remain self-serve and continue using their separate agent keys.