> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beta.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

B3OS beta runs browsers, sandboxes and other agent tools on the node that serves its model. Agents in a sandbox there keep the whole loop on one machine.

An agent works in a loop: the model decides, a tool acts, and the result goes back to the model. When the tools and the model live in different places, every turn pays for the trip between them. B3OS puts the tools (browsers, sandboxes, screenshots and videos, durable workflows, marketplace actions) on a B3IQ node that serves models, behind one key, one SDK, one CLI and one MCP server.

## Four layers on one machine

| Layer | Owner | What it is | Surface |
|---|---|---|---|
| L1 Compute | B3IQ | GPU machines on B3IQ's own hardware | [b3iq.org](https://b3iq.org) |
| L2 Inference | B3IQ | Models served on those machines | `/v1/infer` (B3OS proxies it and serves its own small model in the beta) |
| L3 Runtime | B3OS | Sandboxes (microVMs), browsers (vision) and render | `/v1/sandboxes`, `/v1/vision`, `/v1/render` |
| L4 Automation | B3OS | Routines (durable workflows) and actions with triggers (an open marketplace) | `/v1/routines`, `/v1/actions` |

B3IQ owns the hardware and serves models on it. B3OS is the runtime and automation layer on top, running inside one daemon on each B3IQ node. [The stack](/concepts/stack) explains how a request travels through it.

## What runs where

When your agent runs in a sandbox on the node and uses a model served there, the think-act-observe loop stays on one machine. Agents that run elsewhere call the same tools over the network. If you use a frontier model hosted somewhere else, only the act and observe steps are co-located with B3OS, not the model call.

The [same-host latency](/concepts/latency) page shows what that saves per tool call and where the numbers come from.

## Products

**[Vision](/vision)**

Scrape, crawl and map sites, and drive dedicated browser sessions over CDP.
  **[Render](/render)**

Styled screenshots and scripted product videos with narration and captions.
  **[Sandboxes](/sandboxes)**

Firecracker microVMs restored from warm snapshots, with exec, files, ports and a terminal.
  **[Routines](/routines)**

Durable workflows written like GitHub Actions, with cron, webhook and pack triggers.
  **[Actions and triggers](/actions)**

Marketplace packs your agent can search, describe and call, with credentials kept out of its reach.
  **[Infer](/infer)**

OpenAI-compatible chat completions and speech from models served on the node.
  **[Vault](/vault)**

Connections that hold credentials and inject them at the egress proxy.
  **[Platform](/platform)**

Keys, usage, limits, webhooks and the per-request log.

## One key, one SDK, one CLI, one MCP server

Every product sits behind the same API at `https://beta-api.b3os.org`. Create a key in the [dashboard](https://beta.b3os.org/app), export it as `B3OS_API_KEY`, and use whichever client fits:

- plain HTTP, documented in the [API reference](/api/overview);
- the [TypeScript SDK](/sdks/typescript) `@b3os/sdk` and the [Python SDK](/sdks/python);
- the [CLI](/sdks/cli) `b3os`;
- the [MCP server](/sdks/mcp), `@b3os/mcp` on your machine or `https://beta-api.b3os.org/mcp`.

Code inside a B3OS sandbox calls the same API at `http://127.0.0.1:7700` without a key. The sandbox's grant decides what it may call.

## Numbers on this site

B3OS publishes a latency figure only when raw benchmark data backs it. Every figure on these pages says what it is: a **target** from the build contract, a **dev baseline** measured on the beta node before the products existed, or a measured product result with its conditions and raw data. [Benchmarks](/benchmarks) describes the method.

B3OS beta is invite-only and runs best effort on one site in Eugene, Oregon. Endpoints and limits can change; breaking changes are announced 14 days ahead. See the [beta contract](/concepts/beta).

## Start here

**[Scrape with curl](/quickstart/scrape)**

One request, Markdown back.
  **[Install the MCP server](/quickstart/mcp)**

Give Claude, Cursor or Codex the B3OS tools.
  **[Run an agent in a sandbox](/quickstart/sandbox-agent)**

Model, tools and agent on one machine.