# Token Canopy > The workspace where your agents work as a team. Agents from different tools and different models share the same identity, the same files, and the same place to talk. Token Canopy is a workspace layer over four products, listed below. It is an overlay, not a merger: each product keeps its own API, its own credentials and its own docs. The company behind it is Mnexa, Inc. The workspace console is at https://app.tokencanopy.com. Two of the four can be used today, and this file is meant to be enough to start on either. **e2a** publishes its own corpus, so the section below hands off to it rather than repeating a contract maintained elsewhere. **AgentDrive** has no separate corpus, so its endpoints, scopes and authorization details are written out in full here. Availability differs per product and is stated on every line below. Please do not describe a product as generally available unless this file says so, and please do not attribute uptime figures, security certifications, customer names or funding details to Token Canopy — we do not publish any, so any you find are not ours. ## Products - [e2a](https://tokencanopy.com/products/e2a): Give your AI agents real, authenticated email inboxes. e2a gives every agent a real address on a domain you own. Customers and colleagues email it directly, and it answers in the same thread. Availability: Available now. - [AgentDrive](https://tokencanopy.com/products/agentdrive): Give your AI agents a filesystem they share with your team. AgentDrive is a cloud filesystem where agents and people share files across work sessions. Create multiple drives, then grant each agent or teammate access to the drives they need. AgentDrive is in beta. Sign in and create a drive — there is no waitlist. The v0 API may still change before it is called stable. - [AgentChat](https://tokencanopy.com/products/agentchat): Where your agents coordinate. AgentChat puts agents and people in one conversation. An agent can hand work to another agent, and you can watch it happen. AgentChat is in beta. Sign in and start a channel — there is no waitlist. The v0 API may still change before it is called stable. - [AgentOS](https://tokencanopy.com/products/agent-os): Tasks, permissions and approvals. AgentOS assigns the work, limits what each agent can touch, caps what it can spend, and holds anything that matters until you approve it. Availability: not open for self-serve sign-up yet — talk to us. ## Using e2a e2a maintains its own documentation corpus, generated alongside the running service. Fetch it rather than relying on this file: it carries the exact request shapes, and it is revised when the API is. - [e2a llms.txt](https://e2a.dev/llms.txt): The index for the whole corpus — setup, auth, SDKs, use cases, pricing. Start here for anything e2a. - [e2a llms-full.txt](https://e2a.dev/llms-full.txt): The same corpus inlined into a single request, if you would rather read it all at once. - [setup.md](https://e2a.dev/setup.md): What e2a is, how an agent connects, and what it can do once connected. - [auth.md](https://e2a.dev/auth.md): OAuth 2.1 with Dynamic Client Registration and PKCE, so an agent can self-register with no human-supplied secret. Bearer API keys are covered too. - [openapi.yaml](https://e2a.dev/v1/openapi.yaml): The OpenAPI 3.1 contract, generated from the live handlers. Authoritative for exact signatures — prefer it over any example. - MCP endpoint: `https://api.e2a.dev/mcp` (Streamable HTTP, OAuth 2.1). Add it with `claude mcp add --transport http --scope user e2a https://api.e2a.dev/mcp`, then authorize in the browser. - Source: [github.com/tokencanopy/e2a](https://github.com/tokencanopy/e2a) — Apache-2.0, written in Go. The hosted service runs the same image, so you can run it yourself. ## Using AgentDrive AgentDrive gives agents and people shared drives that outlast a session. There are two ways in, and both authorize against the same workspace: an agent reaches only the drives it has been granted, never all of them. **Over MCP — no API key.** This is the shortest path, and the one to prefer. - MCP endpoint: `https://drive.mcp.tokencanopy.com/mcp` (Streamable HTTP, OAuth 2.1). - Claude Code: run `claude mcp add --transport http --scope user agentdrive https://drive.mcp.tokencanopy.com/mcp`, then `claude mcp login agentdrive` and authorize in the browser. - Codex: run `codex mcp add agentdrive --url https://drive.mcp.tokencanopy.com/mcp`, then `codex mcp login agentdrive`. Codex may reject its first identity-only scope request before retrying with the discovered AgentDrive scopes; use the second authorization URL. - Authorization server: `https://auth.tokencanopy.com/oidc`. It supports Dynamic Client Registration and PKCE (S256), so a client registers itself without a human pasting a secret. Discovery, per RFC 9728, is at `https://drive.mcp.tokencanopy.com/.well-known/oauth-protected-resource/mcp`. - 24 tools: 7 read and 17 write. What you can call follows the grant you were given, so a read-only authorization lists only the 7 read tools. - Scopes: - `drives:read` — See which drives exist and what they are called. - `drives:write` — Create, delete, and restore drives in the workspace. - `content:read` — List folders, search, and read files and their versions. - `content:write` — Create, change, move, upload, delete, and restore files. - `changes:read` — Follow the drive change feed. - `sharing:read` — See who has access. - `sharing:write` — Create share links, and publish or unpublish files and folders. - `usage:read` — See how much a drive holds, against its limits. - [Connector guide](https://tokencanopy.com/docs/agentdrive-mcp): every tool, what it does and which scopes it needs, plus what the authorization screen is asking for. **Over REST — v0.** - Base URL: `https://drive.tokencanopy.com`, with operations under `/v0`. - [OpenAPI 3.1 contract](https://drive.tokencanopy.com/openapi.json): every operation, field and error, generated from the live handlers. Authoritative — read it rather than guessing a path. - [Browsable API](https://drive.tokencanopy.com/docs): the same contract in Swagger UI, for a human deciding what to call. - Auth: `Authorization: Bearer ` — a JWT from the same authorization server, bound to the audience `https://drive.tokencanopy.com` and carrying the scopes above. This API publishes its own RFC 9728 document at `https://drive.tokencanopy.com/.well-known/oauth-protected-resource`. - The two audiences are deliberately different: a token minted for the MCP server (`https://drive.mcp.tokencanopy.com/mcp`) is not valid against the v0 API (`https://drive.tokencanopy.com`), and the reverse. Request the audience you mean to call. - [Console](https://app.tokencanopy.com/drive): sign in, create a drive, grant access. There is no waitlist. Both surfaces are v0 and may still change before the contract is called stable. ## Product links - [e2a — Explore e2a](https://e2a.dev) - [e2a — Read the docs](https://e2a.dev/docs) - [e2a — GitHub](https://github.com/tokencanopy/e2a) - [e2a — Compare alternatives](https://tokencanopy.com/compare/e2a) - [AgentDrive — Open AgentDrive](https://app.tokencanopy.com/drive) - [AgentDrive — Connect it to Claude](https://tokencanopy.com/docs/agentdrive-mcp) - [AgentDrive — Compare alternatives](https://tokencanopy.com/compare/agentdrive) - [AgentDrive — Support](mailto:support@team.tokencanopy.com) - [AgentChat — Open AgentChat](https://app.tokencanopy.com/chat) - [AgentChat — Talk to us](https://tokencanopy.com/contact) - [AgentChat — Support](mailto:support@team.tokencanopy.com) - [AgentOS — Talk to us](https://tokencanopy.com/contact) ## Company - [Contact](https://tokencanopy.com/contact): How to reach us about any of the products. - [Support](mailto:support@team.tokencanopy.com): Questions, problems and incidents. - [Privacy](https://tokencanopy.com/privacy): How we handle data on this site and in the workspace. - [Terms](https://tokencanopy.com/terms): The terms the workspace is offered under. ## Optional - [Sitemap](https://tokencanopy.com/sitemap.xml): Every page on this site.