We built Notte, a browser infrastructure and agents platform.
Many of our users automate UI workflows or extract data from sites that don’t have APIs. In practice, we noticed that once an agent understands how a site works, parts of the task can often run without a browser by interacting with the same network requests the site uses.
So we built Anything API: describe a browser task, and our agent explores the site, builds a function, tests it against your description, and deploys a callable REST endpoint. No infra to manage.
How the build works:
- Describe the task (best results come from writing it as acceptance criteria)
- The agent browses the target site, finds the optimal automation path (UI vs. network requests)
- It generates a function, runs it, checks the output against your description, iterates until it passes
- You get a deployed endpoint running on managed infrastructure
What actually gets deployed:
The agent's default goal is a pure HTTP client that calls the site's backend APIs directly, with no browser at runtime. When the site doesn't expose usable APIs for the task, it produces a hybrid function that mixes API calls with browser automation.
"Can't I just build this with Claude Code?"
Could build a one-off version locally, the difference/value is our managed infrastructure out of the box - concurrent cloud execution, stealth, browser management, scheduling, monitoring
"What happens when the site changes?"
Functions that rely on network requests are typically less affected by frontend changes. Hybrid functions are more sensitive to UI changes, but in either case failures return errors rather than silently failing. Managed self-healing is something we're currently working on.
"Are agents used at runtime?"
Agents drives the build phase. The deployed endpoint is a scripted runtime wherever possible.
"Bot detection?"
Anything API runs on our stealth stack (residential proxies, etc.). However, we enforce a fair use policy. The agent will refuse requests that explictely violate a site's terms of service.
"Authenticated content?"
Works with login-gated sites. The agent handles auth during the build. For recurring runs, we have encrypted credential vaults, session profiles, and OTP interception for 2FA.
We built Notte, a browser infrastructure and agents platform.
Many of our users automate UI workflows or extract data from sites that don’t have APIs. In practice, we noticed that once an agent understands how a site works, parts of the task can often run without a browser by interacting with the same network requests the site uses.
So we built Anything API: describe a browser task, and our agent explores the site, builds a function, tests it against your description, and deploys a callable REST endpoint. No infra to manage.
How the build works: - Describe the task (best results come from writing it as acceptance criteria) - The agent browses the target site, finds the optimal automation path (UI vs. network requests) - It generates a function, runs it, checks the output against your description, iterates until it passes - You get a deployed endpoint running on managed infrastructure
What actually gets deployed: The agent's default goal is a pure HTTP client that calls the site's backend APIs directly, with no browser at runtime. When the site doesn't expose usable APIs for the task, it produces a hybrid function that mixes API calls with browser automation.
"Can't I just build this with Claude Code?" Could build a one-off version locally, the difference/value is our managed infrastructure out of the box - concurrent cloud execution, stealth, browser management, scheduling, monitoring
"What happens when the site changes?" Functions that rely on network requests are typically less affected by frontend changes. Hybrid functions are more sensitive to UI changes, but in either case failures return errors rather than silently failing. Managed self-healing is something we're currently working on.
"Are agents used at runtime?" Agents drives the build phase. The deployed endpoint is a scripted runtime wherever possible.
"Bot detection?" Anything API runs on our stealth stack (residential proxies, etc.). However, we enforce a fair use policy. The agent will refuse requests that explictely violate a site's terms of service.
"Authenticated content?" Works with login-gated sites. The agent handles auth during the build. For recurring runs, we have encrypted credential vaults, session profiles, and OTP interception for 2FA.
Try it and let us know what you think: https://anything.notte.cc
- Andrea & Lucas, Notte Founders