Skip to main content
Yambr is a managed deployment of Open Computer Use. Four public services, each with a distinct job:
Yambr publishes MCP only. api.yambr.com is not an LLM gateway. /chat/completions, /completions, /embeddings are closed. Your LLM traffic goes to your own provider (OpenAI, Anthropic, a self-hosted LiteLLM, …); your Yambr key unlocks the Computer Use tools.

​
How they talk to each other

cu.yambr.com is not an MCP endpoint. It hosts sandboxes and serves artifact URLs. The public MCP endpoint is https://api.yambr.com/mcp/computer_use — call that with your Yambr key. See cu.yambr.com.

​
When to use what

API keys

Sign in with GitHub/Google, get approved, manage up to five keys with live spend.

LiteLLM gateway

The MCP endpoint — https://api.yambr.com/mcp/computer_use. Three ways to wire it in.

Hosted chat

chat.yambr.com — no-setup Open WebUI with Computer Use, models ready to go.

cu.yambr.com

Sandbox containers and public artifact URLs.

Access model

Why MCP-only, and how bring-your-own-model actually works.

Dashboard tour

Walk-through of every screen at app.yambr.com.

​
Managed vs self-hosted

See Self-hosting quickstart for the DIY path.