Notte · Rate Limits

Notte Rate Limits

Notte governs usage primarily through plan-based operational limits and a credit balance rather than fixed per-endpoint request rates. Each subscription tier caps browser concurrency (Free 5, Developer 25, Startup 100), concurrent agents/functions (Developer 25, Startup 100), and maximum session length (Free 15 min, Developer 120 min, Startup 300 min, hard cap 1440 min). Sessions also enforce an idle timeout (default 3 min, max 15). Agents are bounded by a max_steps parameter (1-150, default 20). When the credit balance is exhausted or a concurrency/duration ceiling is hit, further work is blocked until credits are topped up or capacity frees. Specific per-endpoint HTTP request rates are documented at the API reference rate-limits page and are not reconciled in this artifact.

Notte Rate Limits is the machine-readable rate-limit profile for Notte on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring concurrent_browsers, concurrent_runs, minutes, steps, and credits.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, Web Agents, Browser Automation, Sessions, and Scraping.

6 Limits Throttle: 429
AIWeb AgentsBrowser AutomationSessionsScrapingRate LimitingQuotasThrottling

Limits

Browser Concurrency account
concurrent_browsers
5 (Free) / 25 (Developer) / 100 (Startup) / custom (Enterprise)
Maximum simultaneously open cloud browser sessions.
Concurrent Agents / Functions account
concurrent_runs
25 (Developer) / 100 (Startup) / custom (Enterprise)
Maximum simultaneous agent and function runs.
Max Session Duration session
minutes
15 (Free) / 120 (Developer) / 300 (Startup); hard cap 1440
max_duration_minutes per session; default 15, maximum 1440.
Session Idle Timeout session
minutes
3 default, 15 max
idle_timeout_minutes; session closes after inactivity.
Agent Max Steps agent
steps
20 default, 1-150 range
max_steps bounds how many actions an agent run may take.
Credit Balance account
credits
per plan allowance plus top-ups
Work halts when credits are exhausted; sessions/functions/proxies/LLM tokens draw down credits.

Policies

Plan-Based Limits
Concurrency, session duration, and credit allowances raise as accounts move from Free to Developer to Startup to Enterprise.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.
Credit Top-Up
Exhausted credit balances can be replenished via non-expiring manual top-ups to continue running.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/notte-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.