Accesses
Share assistants with people outside your workspace through an MCP server and an HTTP API, public or protected by keys, with credit ceilings.
An access gives people outside your workspace a way to ask some of your assistants: your clients, a partner, the agents of another team. They get an address, never an account. Your workspace pays for every question asked through it.
What an access holds
| Part | What it is |
|---|---|
| Assistants | One to 20 of your assistants, each with a description that callers read: what it answers, from what. Their context, guidelines and resources stay private. |
| What callers can do | Eco, Flash and Deep answers at their usual prices, and passage search at 1 credit. Turn off what you do not want to pay for. |
| Protection | Anyone with the address, or clients with a key (Pro plan): each client gets its own key, which you revoke on its own. |
| Spending | A ceiling in credits per day and per month, on the access and on each key. A call that would pass it is refused until the next day or month. |
Connecting
Open the access, then Connect. Every access has:
- an MCP server address, for Claude Code, Cursor, Claude Desktop, Claude.ai and ChatGPT (Claude.ai and ChatGPT add a connector without a key, so they reach public accesses only);
- an HTTP API, with a help page that lists its endpoints, parameters and errors.
Questions asked through an access show in your Logs and Usage, marked with its name.
Turning it off
The Live switch stops every call at once and keeps the access as it is. Delete revokes its keys for good; what it spent stays in Usage.