Give your agent
the internet.

Launch an isolated browser in China or overseas, observe what it sees, move safely between agent and human control, and keep every action and charge attached to one task.

Create your first browser →Copy the agent prompt

Sandboxed browserOne isolated session with bounded runtime and exact cleanup. Auth & profilesRestore encrypted, account-bound login state without exposing it. Regional routingChoose China or overseas capacity independently from proxy egress. Observable runsVisual frames, semantic snapshots, real tabs, audit, and usage.

Start here

From zero to a controlled browser.

01 · CreateReserve a browserSet region, preview mode, URL, profile, and timeout. 02 · ControlAcquire agent controlUse a fenced capability before navigation, input, or tabs. 03 · ObserveVerify the resultInspect a fresh snapshot or frame, then stop in guaranteed cleanup.

Fast setup

Copy one prompt into your coding agent.

The prompt tells an agent where the authoritative MASAKA contracts live, how to obtain credentials without leaking them, which browser interface to choose, and how to clean up every session.

Agent onboarding prompt

Use MASAKA for this task: [describe what you want to build or automate].

First read the machine-readable manifest at https://masaka-ai.vercel.app/.well-known/masaka-agent.json, GET https://masaka-backend.vercel.app/api/capabilities, then read https://masaka-ai.vercel.app/docs/llms.txt and the quickstart at https://masaka-ai.vercel.app/docs/quickstart/.

If MASAKA credentials already exist, validate and reuse them. Otherwise ask me to sign in at https://masaka-ai.vercel.app/dashboard.html and create a project API key. Keep API keys, control capabilities, view tickets, profile state, credentials, and checkout data out of chat, logs, source code, commits, and generated files.

Choose the least-powerful MASAKA interface that fits this project: trusted server SDK, REST API, signed-in web client, or Agent Harness. Agent Harness uses MASAKA browser tools with Browser Use browser-harness helpers; it is not Browser Use Cloud and is not a general CDP endpoint.

Create a browser with an explicit region ("china" or "overseas"), bounded max_seconds, and the required visual or semantic preview. Wait for running, acquire agent control, and inspect a fresh snapshot before using coordinates. Snapshot also returns the real open tabs and active_tab. Use tabs to refresh them; only use tab_switch or tab_close with a returned handle, and use tab_new for a new real tab. Never invent a tab handle.

Do not retry a timed-out mutation because its outcome is unknown. Inspect its command receipt. Payment is not an automatic human handoff. When the task includes a pre-authorized spend policy with merchant scope, currency, a per-transaction limit, a total budget, and a payment-instrument reference, complete purchase and payment end to end. Immediately before commit, re-read the merchant, item or service, total, and currency; use an idempotent order key; then verify merchant or provider confirmation. Pause only when the policy is missing or exceeded, the merchant or total changes, the payment instrument is unavailable, CAPTCHA or strong customer authentication requires user presence, or the mutation outcome is unknown. Login, deletion, posting, and other actions outside granted authorization still require human help. Always stop temporary sessions in guaranteed cleanup.

Complete the task and report what ran, what was verified from fresh browser evidence, all created artifacts, actual usage, and any remaining human action.

API quickstart

Create the first browser.

Create an API key in Dashboard → API keys, keep it on a trusted server, and send an explicit region and deadline.

cURL

curl https://masaka-backend.vercel.app/api/sessions \
  -H "Authorization: Bearer $MASAKA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Research task","url":"https://duckduckgo.com/","region":"overseas","preview_mode":"visual","max_seconds":300}'

Production path

Develop, verify, then scale by demand.

1
Discover the live contract
Read the agent manifest and capability response before generating integration code.
2
Develop against a bounded session
Use a short timeout, one region, and guaranteed cleanup.
3
Attach a profile or App only when useful
Keep authenticated state and repeated task policy explicit.
4
Observe usage and capacity
Regional workers expand from queue demand and host headroom.

IntegrateAgent HarnessObserve, act, verify, and hand control to a person safely.OperateElastic workersDemand-driven capacity without a manually configured fleet ceiling.AccountExact usagePer-second browser runtime and model-token charges.