If you use an AI coding assistant, paste this prompt into Cursor, Claude Code, or Windsurf:

1. Create an account

The free plan includes 10 browser hours and 500 actions per month with 3 concurrent sessions. It requires no credit card.

2. Get an API key

In the dashboard, open API Keys and create one. Keys look like ph_live_…. The key is shown once at creation and stored hashed, so copy it immediately; it cannot be retrieved later. If you lose it, revoke it and mint a new one. Keep keys server-side, because a key grants full control of your browser sessions.

3. Create a session

The response includes connect_url, so you can attach immediately with no second call.
Read this before you build. connect_url is returned only by this call and by /connect. Reading a session back with GET /v1/session/{id} returns connect_url: null by design. See Connecting a browser for the reasoning and what to do instead.

4. Attach Playwright

Tilion speaks the Chrome DevTools Protocol, so any CDP client works unchanged.
A session already has one browser context with one page open. Use those rather than calling newContext() / newPage(), or you will pay for a second renderer you do not need.

5. Release the session

Sessions are billed while they exist, so release them explicitly:
The call returns 204 No Content. Every session also has an idle timeout and is reclaimed automatically, but do not rely on that for cost control. Always release in a finally block.

Fetch a page without driving the browser

If you only need page content, skip the CDP client. Create a session as above, then ask for the page in one request:
The full options are on the Fetch page.

Next steps

  • Connecting a browser covers CDP, tokens, and reconnecting.
  • Sessions covers lifecycle, modes, and timeouts.
  • Fetch covers getting page content without driving a browser.
  • Errors and Limits cover every status code, quota, and rate limit.