Team0 developer resources
Give your agent the context it should not have to rebuild.
Team0 exposes a Streamable HTTP MCP server for self-serve agent connections and an allowlisted External API beta with OAuth 2.0 discovery and named scopes. Use MCP when an agent needs the maintained business understanding behind a user's Chief. Use the source system's own MCP when all you need is one raw calendar event or inbox lookup.
MCP — self-serve
Create a revocable t0c2c_ key in Agents → Connect an agent. Configure https://api.team0.ai/mcp/mcp as a remote Streamable HTTP server and send the key in Authorization: Bearer. The Chief answers from the Team0 World Model; the server does not expose a raw customer-data read tool.
OAuth 2.0 — allowlisted beta
Approved developer applications use Authorization Code with PKCE S256 through Team0's Clerk issuer. Authorization-server metadata is published at /.well-known/oauth-authorization-server. The Team0 resource server publishes its named least-privilege scopes at /.well-known/oauth-protected-resource. The beta is allowlisted; email hey@team0.ai for access.
Machine-readable discovery
Read the Team0 OpenAPI document, the MCP discovery document, llms.txt, or the expanded llms-full.txt. The canonical API origin is https://api.team0.ai; the canonical MCP endpoint is https://api.team0.ai/mcp/mcp.
Agent onboarding
No sales call required for MCP.
New users can start a seven-day full-access trial without a credit card, connect the sources their Chief should understand, and create an MCP key from the Agents workspace. The secret is shown once and can be rotated or revoked later. Team0 does not yet publish a separate anonymous sandbox with synthetic customer data; integrations should test against their own trial workspace and avoid production credentials in logs or examples.
GET /.well-known/mcp.json · GET /openapi.json · GET /llms.txt