Discovery: would a Notte hosted-browser tier fit the cascadeflow provider model?

[sam-notte]

Hi @lemony-ai team,

Sam from Notte (notte.cc, hosted browser infrastructure for AI agents). I just read through the cascadeflow README, liked the "per-tool-call budget gating" and "runtime stop/continue/escalate" framing.

The reason I am filing an issue rather than opening a PR: I want to confirm fit before writing code.

The shape of the question

Cascadeflow already lists OpenClaw and Hermes Agent as supported providers. Browsers are another natural cascade dimension: a task might be solvable by a simple curl/requests fetch (cheap), or might need a real browser (moderate cost), or might need a hosted anti-bot browser with residential proxies and captcha solving (highest cost).

Would a notte provider in cascadeflow fit your roadmap, or do you see "browser tiering" as outside the scope?

If yes, I would open a PR with the same shape as your existing Hermes/OpenClaw integrations. If no or "not yet", that is useful too. Saves your review time.

Quick context on Notte (in case useful)

• Hosted browser SDK + MCP server for AI agents
• Built-in residential proxies, captcha solving, stealth sessions, credential vault for authenticated sites
• "Functions" feature: deploy any browser automation as a scheduled serverless API endpoint
• Open source: github.com/nottelabs/notte (1,953 stars, Python SDK + MCP server)

Happy to defer entirely if cascadeflow's focus is purely LLM/model routing rather than tool/browser tiering.

Cheers,
Sam
sam@notte.cc · github.com/nottelabs

[sam-notte]

Following up: one thing that may be relevant to cascade-routing logic.

On per-hour pricing across hosted browser providers (browserarena.ai numbers, disclosure: Notte runs the benchmark, it is OSS at github.com/nottelabs/browserarena), the spread is $0.05 to $0.12/hr.

So the "hosted anti-bot browser" tier is not a step-change in cost from a basic real-browser tier, which changes the calculus for when to escalate. Just flagging in case the data is useful for whatever you decide on browser-routing scope.