Skip to main content

​
Overview

A browser in Rusty Browser is a fully managed, isolated browser instance. You create it, issue commands, and delete it when done. Billing runs for the duration the browser is open.

​
Lifecycle

PUT /v1/browsers/        → browser created, billing starts
  POST /:id/navigate/
  POST /:id/click/
  POST /:id/instruct/
  ...
DELETE /v1/browsers/:id/ → browser closed, billing stops

​
Billing

Browsers are billed by the hour from the moment they’re created until they’re deleted.
  • 50 tokens/hr on Pay As You Go
  • Subscription plans lower the per-hour rate — see Pricing
  • Idle browsers still consume tokens — always delete when finished

​
Best Practices

  • Always delete browsers when your task is complete
  • Use defer client.DeleteBrowser(...) in Go to guarantee cleanup
  • Don’t create browsers before you need them — billing starts immediately on creation
  • For long-running tasks, monitor your token balance from the dashboard

​
Isolation

Each browser runs in a completely isolated environment:
  • Fresh state on every creation — no cookies, cache, or history carried over
  • No shared state between browsers
  • Failures in one browser do not affect others