# Ringbop documentation

> Give your agent a phone. Connect an AI assistant to Ringbop, make user-authorized phone calls, and bring back transcripts and results.

Ringbop is in developer preview. It connects to Codex, Claude Code, Cursor,
and compatible hosted MCP clients using browser OAuth sign-in. The optional local installer supports macOS,
Linux, and Windows through WSL. Other clients use manual MCP configuration;
Instinct compatibility is unverified.

## Start here

- [Setup prompt](https://ringbop.com/llms-install.md): copy into an assistant to handle installation and check the connection.

- [For agents](https://ringbop.com/llms.mdx/agents): installation, browser sign-in, tool discovery, calling workflow, retries, and revocation.
- [MCP tool schemas](https://ringbop.com/mcp-tools.json): generated input schemas for all six tools.
- [Website](https://ringbop.com/): quick installation and expandable instructions for each assistant.
- [Account](https://ringbop.com/account): sign in to verify your phone and view your call history.

## How it works

1. Paste the setup prompt into the assistant, or add https://ringbop.com/api/mcp as a remote MCP server. The agent guide has instructions for each assistant.
2. The user signs in in their browser and approves the connection. No API key needs to be copied.
3. The assistant loads Ringbop's native MCP tools and checks the connection with `get_account`.
4. When the user authorizes a call, the assistant submits it, keeps the call ID, and retrieves the result asynchronously.

Hosted MCP connects directly to Ringbop with Clerk OAuth and S256 PKCE. A local STDIO connector remains available as a fallback. Remote HTTP clients use `https://ringbop.com/api/mcp` with a securely managed Clerk bearer token; the website URL alone is not an MCP endpoint. For headless
containers or SSH, add `--headless` to the installer, keep it running, and open
the printed approval link on any computer or phone. Match the code and approve
in Clerk; the worker completes setup automatically without a browser or inbound
port. SSH and Linux without a graphical display select this mode automatically.
See the agent guide for persistent storage and tool-loading requirements.

## Early access

All signed-in accounts can call user-supplied eligible destinations without
per-number operator approval. Installation alone does not authorize a call.
Calls can incur charges, and the account's current regions and limits govern
calling. Private account data and calling tools require authentication. Global
suppression and recipient opt-outs apply to every account.

## Downloads and machine-readable documentation

- [Shell installer](https://ringbop.com/install.sh)
- [Python installer](https://ringbop.com/ringbop-install.py)
- [Python MCP connector](https://ringbop.com/ringbop-mcp.py)
- [Documentation index](https://ringbop.com/llms.txt)
- [Complete documentation](https://ringbop.com/llms-full.txt)

Documentation is available without authentication or JavaScript. `/llms.mdx`
and `/llms.mdx/agents` return Markdown directly.

HTTP integrations can use `--headless --auth-only` to sign in without installing
a STDIO server. See the agent guide for direct HTTPS approval, token refresh,
MCP messages, and REST routes. Hosted clients use Clerk client registration, browser consent, and resource-bound OAuth tokens. Local fallback clients can keep their existing saved connections.

## Pricing

The first 2 connected minutes are free, no card required. Paid balance then continues the call at $0.50 per connected minute, billed by the second, until the balance is exhausted. $5 prepaid top-ups through card checkout or compatible MPP card wallets fund the same account. No subscription. Manage balance and optional automatic refill at https://ringbop.com/account/billing. See the agent guide for payment endpoints and the `add_funds` tool.