Skip to main content
Tilion provides Chrome sessions for browser automation. You can read pages, interact with elements, and connect through Playwright or CDP. There are two ways in:
  • An AI agent connects to the MCP server at https://back.tilion.dev/mcp and signs in with OAuth. This is the first option for an agent: the owner approves once on Tilion’s page and no key is created or pasted. Follow Agent setup. An agent asks for an API key only when its product cannot connect an MCP server.
  • Code calls the REST API at https://back.tilion.dev with a bearer API key that has the ph_live_ prefix.

Set up with an AI agent

To have Claude Code, Codex, Grok, claude.ai, ChatGPT or Muse set Tilion up for you, follow Agent setup. It gives the prompt to paste and says what you approve.

Start with a working example

The quickstart creates a session, fetches a page, and closes the session. Choose Python, Node.js, or curl.

Choose a task

Create a browser

Configure session lifetime, region, and proxy routing.

Read a protected page

Fetch rendered text with challenge recovery and job polling.

Extract Markdown

Get Markdown and page metadata with an output-size limit.

Drive a page

Find elements and interact with them over HTTP.

Sessions and state

A session retains cookies and browser storage between requests. Reuse it for related page operations. To preserve a site’s login across sessions, save its cookies or use a browser profile. Sessions end when deleted or when a lifetime or inactivity limit is reached. Browser time is metered until then. Close sessions explicitly when your work finishes.

Guides and reference

Guides provide examples for common tasks. The API Reference tab contains request fields, response schemas, and route-specific errors. For an MCP client, use the MCP server reference. For an AI agent, start at Agent setup, also served as /agents/setup.md. Machine-readable documentation is available at /llms.txt and /llms-full.txt.