> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Browser Overview

> Isolated, short-lived browser sessions for AI agents — navigate, observe, click, fill, and screenshot through one API.

Agent Browser gives your application an isolated, short-lived Chromium instance through one API: create a browser session, navigate to pages within an allowed domain list, observe the DOM to get element references, interact with elements (click, fill, select), and take screenshots.

It is built as a primitive for AI agents — every action returns structured JSON ready to feed a model as tool output. The semantic observation model means agents interact with element references instead of pixel coordinates.

## What You Can Do

| Capability | Endpoint | Returns |
| - | - | - |
| [Create Session](/docs/agent-browser/sessions) | `POST /v2/browser_sessions` | An isolated browser session |
| [Navigate](/docs/agent-browser/actions) | `POST /v2/browser_sessions/:id/actions` | Page load with URL and title |
| [Observe](/docs/agent-browser/observations) | `POST /v2/browser_sessions/:id/actions` | Element references (`refs`) and a text tree of the DOM |
| [Click / Fill / Select](/docs/agent-browser/actions) | `POST /v2/browser_sessions/:id/actions` | Interaction with elements by ref |
| [Screenshot](/docs/agent-browser/actions) | `POST /v2/browser_sessions/:id/actions` | A downloadable screenshot artifact |
| [Batch](/docs/agent-browser/actions) | `POST /v2/browser_sessions/:id/actions` | Multiple actions in one request (1–50, sequential) |

## Next Steps

> **[Get Started](/docs/agent-browser/getting-started)**
>
> First session to screenshot in a few minutes.

> **[Sessions](/docs/agent-browser/sessions)**
>
> Session lifecycle, allowed domains, and limits.

> **[Actions](/docs/agent-browser/actions)**
>
> All action types, batch, and the interaction loop.

> **[Observations](/docs/agent-browser/observations)**
>
> The observe → ref → click/fill flow explained.
