Skip to main content
Read the Notte skill and follow its setup instructions when setting up Notte or building browser automation. This is the shared source for CLI setup, authentication, and the browser-to-code workflow.
Usage is paid from dollar-based credits (see Pricing). These are the safeguards that keep spend predictable.

​
Keep sessions short

Sessions close on their own after an idle timeout or a maximum duration. Both are set per session. The idle timeout cannot exceed the maximum duration, so raise max_duration_minutes first if you need a longer idle timeout. Set both to the shortest values your workflow needs. See Session lifecycle for details.

​
Turn off proxies you don’t need

Built-in proxies are on by default and are billed per GB. Set proxies to false for sessions that don’t need them. See Proxies for rates.

​
Plan allowances

Some plans cap spend per source: LLM, proxy, browser sessions, workflow runs and agent tool calls. The Included usage card on the Limits page under Billing in the console shows how much of each allowance you have used and when it resets. When an allowance is used up:
  • With a payment method on file, further usage is billed to your card at the end of the period.
  • Without one, new work for that source is rejected with a 402 until the period resets, you add a payment method, or you upgrade your plan.

​
Emails

Notte sends an email when:
  • 80% of your plan’s credits are used.
  • Your credits run out. New sessions are blocked and scheduled functions are paused. Top up to start new sessions again, then resume the paused schedules with client.functions.resume_schedules(function_id).
Top up from the billing page.

​
What doesn’t exist yet

There is no workspace-level monthly spending cap that you set yourself. Limits come from your plan’s allowances and your credit balance.