# Browserious

Hosted, isolated Chromium sessions for agentic workflows, controlled over an API.

The page your agent fetched was empty. A page that builds its content in the client returns a
script tag and an empty container to a plain HTTP fetch. Browserious gives an agent a real,
isolated Chromium session over an API, so it can render that page, interact with it, keep a
signed-in profile and return a screenshot.

## One run, start to artifact

The landing page shows a recorded run, not a live one: loading it starts no browser and spends
nothing. The run opened a small demonstration page whose body is empty until its script executes,
clicked the control that switches the report to its "Last 30 days" range, and saved the screenshot
the browser produced. Two ids come back and both are needed: session create prints a session id, and page create
prints a page id, page-1 for the first page in a session. The quoted values below are placeholders
to replace with your own.

    browserious session create
    SESSION="00000000-0000-0000-0000-000000000000"
    browserious page create "$SESSION" --url "$PAGE_URL"
    PAGE="page-1"
    browserious page click "$SESSION" "$PAGE" "Last 30 days" --strategy text
    browserious screenshot page "$SESSION" "$PAGE" --output-file report.png
    browserious session delete "$SESSION"

Deleting the session stops the browser and ends billing for it. Saved profiles and uploaded files
are separate from the session and stay under their own retention rules until you delete them.

## What a browser adds that a fetch cannot

- Rendered content. Pages that build themselves in the client return a script tag and an empty
  container to a plain fetch. A browser runs that script and reads the result.
- Interaction. Filters, pagination, expanding sections and multi-step forms only exist once
  something clicks them.
- Visual verification. Screenshots let a model check what a layout actually looks like, rather
  than inferring it from markup that may not reflect the painted result.
- Persistent state. Profiles keep cookies, storage and signed-in sessions between runs.
- Localhost access. A tunnel points a hosted session at a port on your own machine, so an agent
  can open the application you are building before it ships.

## Quick start

Install the CLI. It is one Python distribution; use `uvx browserious` instead if you would rather
not install anything persistently.

    pip install browserious

Sign in. This is RFC 8628 device authorization: it prints a URL and a code, you approve it in a
browser, and the CLI stores a refreshing token. There is no API key to copy.

    browserious login

Run the browser. `browserious session create` prints the session id; put that id in SESSION and
use it in the commands that follow. Deleting the session at the end stops billing for that
browser.

    browserious session create
    SESSION="00000000-0000-0000-0000-000000000000"
    browserious page create "$SESSION" --url https://example.com
    PAGE="page-1"
    browserious screenshot page "$SESSION" "$PAGE" --output-file result.png
    browserious session delete "$SESSION"

## Using an MCP client instead

The MCP server reuses the credential that `browserious login` stored, so the configuration carries
no secret.

    {
      "mcpServers": {
        "browserious": {
          "command": "uvx",
          "args": ["browserious", "mcp"]
        }
      }
    }

## What it costs to run

Credits buy two things: browser session time and network traffic. Stored data is not metered. New
accounts start with a welcome balance. Current rates, pack sizes and expiry rules are on the
pricing page.

## Agent skill

A packaged, versioned Browserious skill is being prepared. It is not published yet, so there is
nothing to download today. Until it lands, the API documentation and the quick start above are the
canonical instructions.

## Destinations

- Home: https://browserious.com/
- Pricing: https://browserious.com/pricing
- Quick start: https://browserious.com/#quickstart
- API documentation: https://api.browserious.com/docs
- Terms & Conditions: https://browserious.com/terms
- Privacy Policy: https://browserious.com/privacy
- Refund Policy: https://browserious.com/refunds
- Support: support@browserious.com

Operated by IP Arseniy Potapov.