Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.notte.cc/llms.txt

Use this file to discover all available pages before exploring further.

STOP. Do not read past this section until you have read and followed /quickstart.md.Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live observe() call, CLI notte page observe output, or generated workflow code. Guessed browser targets fail on real pages.Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with notte sessions workflow-code before using SDK docs or SDK code.SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior.
When you exceed rate limits, the API returns a 429 status code. Implement backoff to handle this gracefully.

Exponential backoff

import time
from notte_sdk import NotteClient
from notte_sdk.errors import NotteAPIError

client = NotteClient()

def request_with_backoff(max_retries=3):
    for attempt in range(max_retries):
        try:
            with client.Session() as session:
                return session.scrape(url="https://example.com")
        except NotteAPIError as e:
            if e.status_code == 429:
                wait_time = 2 ** attempt  # 1, 2, 4 seconds
                print(f"Rate limited. Waiting {wait_time}s...")
                time.sleep(wait_time)
            else:
                raise
    raise Exception("Max retries exceeded")

Best practices

  1. Implement backoff — Always handle 429 responses with exponential backoff
  2. Batch requests — Combine multiple operations when possible
  3. Cache responses — Avoid redundant API calls by caching results

Increasing limits

Need higher limits? Contact us to discuss enterprise options.