---
name: browser-session
description: Lease one ordinary remote browser with standard CDP access for 10 minutes through Ausca.
---

# Ausca Browser Session

Use this service when an agent already knows how to drive CDP, Playwright, or
Puppeteer and needs a short-lived remote browser without creating an account.
It is browser infrastructure, not a browser agent.

## What the purchase includes

One paid invocation creates or exactly replays one 10-minute browser lease. The
result includes a session id, expiry, and an opaque bearer capability. Status,
CDP connection creation, and close do not charge again.

The service does not provide actions, extraction, crawling, recording,
persistent profiles, proxies, stealth, CAPTCHA solving, or a target-success
promise.

## Invoke

Invoke the exact `ausca/browser-session` package through the caller's skill
runtime. The runtime resolves immutable live terms and routes the paid call to
`https://ausca.com/v1/invocations`. The service input is `{}`; there are no
caller-selected browser options in this release.

After an authorized purchase, read `resource_result.resource_access` from the
verified paid-invocation readback. Keep its capability in host-controlled secret
state. Never place it in a prompt, log, receipt, or later model-authored tool
argument.

## Use the lease

Supply `Authorization: Bearer <capability>` to the canonical Ausca lifecycle:

1. `GET /v1/browser-sessions/{session_id}` for status and hard expiry.
2. `POST /v1/browser-sessions/{session_id}/connections` with a stable
   `Idempotency-Key` to mint a short-lived CDP WebSocket ticket.
3. Connect to the returned `wss://browser.ausca.com/...` URL using an ordinary
   CDP client.
4. `DELETE /v1/browser-sessions/{session_id}` to close early, or allow the hard
   10-minute expiry to clean it up.

Connection tickets are short-lived and single-use. Reuse the purchase
idempotency identity only for the same intended lease. If the paid response is
uncertain, replay that exact purchase; never mint a second payment identity.

The active catalog revision and linked schemas are the machine authority. x402
uses its external V2 semantics; Ausca's internal contracts remain V1.