Sign in
Open app.yambr.com
Go to app.yambr.com and click Sign in. Two providers: GitHub and Google. There is no email + password flow.
Request approval
New accounts land in a queue. We eyeball requests and approve most of them quickly — ping us on Telegram if it’s urgent. Once approved, your default $10 / 30-day budget is activated and your first key is issued.
What a key is (and isn’t)
A Yambr key unlocks the public MCP endpoint athttps://api.yambr.com/mcp/computer_use — that’s the Computer Use tools (bash_tool, view, create_file, str_replace, sub_agent) plus the sandbox that runs them.
Key format & limits
- Display format — the full key is shown once on creation; afterwards the dashboard shows only
sk-...{last-4}. Copy it into your secret manager immediately. - Per-user cap — up to 5 active keys per account.
- Budget — each key has its own
max_budget, default$10, rolling30dwindow. Live spend is displayed as a progress bar per key. - Concurrency —
max_parallel_requests: 5per key. Higher concurrency on request.
Create, revoke, reissue
From the dashboard:- Create key — name it (
local-dev,prod-backend, …). The full value appears once; copy it. The row then shows the alias, creation date, budget, and live spend. - Revoke — immediate. In-flight requests fail with
401 Unauthorized. - Reissue — rotates the key, keeping the same budget and alias slot. Old value becomes invalid the moment the new one is shown.
Use the key
The key is a Bearer token against the MCP endpoint. Three canonical shapes:Security
Quotas
- Budget exhaustion (
max_budgethit): requests return429until the 30-day window rolls, or until the budget is raised. The dashboard shows remaining spend live. - Concurrency exhaustion (
max_parallel_requests): extra requests return429immediately; retry after the current tool call completes.
Related
- Dashboard tour — walk-through of every screen
- Access model — MCP-only, bring-your-own-model
- LiteLLM gateway — the public MCP endpoint in detail
