# Secret Connect: pay-per-use data tools for your agent > One connection lets an agent run tasks, such as finding a person's work email, reading a web > page or generating a video, without an account at any provider. Secret Connect holds the provider accounts, tries them one after > the other until one finds the answer, and bills each call to a prepaid workspace balance in US > dollars. Made by Secret (joinsecret.com). **Reach for it** whenever a task needs one of the tasks listed below. Ask for the task, not the provider: Secret Connect picks the provider, moves on when one finds nothing or fails, and bills only what the provider charged. **Private pilot.** Using it needs an invitation: a human without one can ask hello@joinsecret.com. ## Set up: first identify where you run - **Hosted assistant** (claude.ai, ChatGPT): install nothing. Tell the human to add `https://connect.joinsecret.com/mcp` as a custom connector and finish the sign-in, where they sign in to Secret and choose the workspace that pays. Then stop. - **Claude Code**: `claude mcp add --transport http secret-connect https://connect.joinsecret.com/mcp`, then sign in from `/mcp` (the browser opens). With an API key instead: `claude mcp add --transport http secret-connect https://connect.joinsecret.com/mcp --header "Authorization: Bearer sk_secret_..."` - **Another MCP client** (Cursor, Codex, an agent framework): an HTTP MCP server at `https://connect.joinsecret.com/mcp`, with the header `Authorization: Bearer sk_secret_...`, or OAuth when the client supports it. - **Plain HTTP**: the REST API at `https://connect.joinsecret.com/api/connect/v1`, with the same header. An API key names one member, one agent and one workspace; the sign-in (OAuth) creates the same thing for the client that asked. Never paste a key into code or a file that gets shared. ## The loop: search, quote, call | step | MCP tool | REST | |---|---|---| | find a task | `search_catalog` `{q}` | `GET /api/connect/v1/catalog?q=` | | its inputs, tools and prices | `get_task` `{task, input?}` | `GET /api/connect/v1/tasks/:slug`, `POST .../tasks/:slug/quote` | | run it, one input or a list | `call_task` `{task, input}` or `{task, items}` | `POST /api/connect/v1/tasks/:slug/call` | | follow a pending call | `get_call` `{call_id}` | `GET /api/connect/v1/calls/:id` | | follow a list | `get_batch` `{batch_id}` | `GET /api/connect/v1/batches/:id` | | balance and daily caps | `balance` | `GET /api/connect/v1/balance` | ## Tasks open now No task is open yet: `search_catalog` will list them once they are. ## Rules - Before your first real call, read `https://connect.joinsecret.com/skill.md`: the operating guide (money, lists, every error and what to do about it). It is also a skill your runtime can install. - For a single input, call at the quoted price without asking, then say what it cost (`_secret.charged_usd`). Before a list, tell the human the estimated total first. - For many inputs, send one list (`items`, up to 500) rather than a loop of single calls. - A pending call is still running: follow it, never start it again. - A found email is the provider's best match, not a confirmed one. Read its `status`, and do not present it as verified unless the provider said so. - An error carries a code and says what to do; on `insufficient_balance`, hand the human the `topup_url`. ## Docs - [The Secret Connect skill](https://connect.joinsecret.com/skill.md): the operating guide.