The AI platform for web automation. Browsers, data APIs, and functions for you and your AI agents. Connect via CLI, MCP, or SDKs. Join 20k+ builders.
San Francisco
Joined December 2024
- Tweets638
- Following10
- Followers9.7K
- Likes1.4K
Pinned Tweet
Browser now costs $0.01 per hour on @nottecore 🖤
→ Up to 12x cheaper and 7x faster!
→ one browser running all day: 24 cents
→ 1,000 browsers for an hour: $10
Ask your agents to run browsers on Notte:
notte.cc/skill.md
Notte x @daytonaio
In Anything API, every conversation gets its own sandbox, and about a quarter of them end up needing a browser.
Our CTO @lucas_gdno wrote on Daytona's blog about how we run the two together: daytona.io/dotfiles/daytona-…
Now on @nottecore
We forked BELL and plugged @nottecore browsers
Same personal agents builder. Same iMessage flow. Same Link checkout. Up to 12x cheaper and 8x faster browser sessions for your agents 🖤
Agents that browses shouldn't cost more than you do
→ $0.01 per browser hour
→ benchmarks on browserarena.ai
→ fork it: github.com/nottelabs/bellsta…
Very excited to be part of the @e2b ecosystem ‼️
Two new integrations landed in the E2B Cookbook this week: @veris_ai and @nottecore.
1. Veris
Use Veris with E2B to simulate any system your agent needs to work with, so it can test its work in a stateful and consistent twin of your production environment.
Agents can claim they did things they didn’t. In the cookbook example, the agent creates a Stripe customer in the simulation, and Veris’s receipt confirms the API call actually happened.
Cookbook: github.com/e2b-dev/e2b-cookb…
2. Notte
Use Notte with E2B to give your agents a real browser that can get past bot checks, while the sandbox stays lightweight.
Real sites check for bots, ask for captchas, and want you signed in. Notte handles all three with stealth, residential proxies, captcha solving, and saved logins, so your sandbox stays focused on the agent's code.
Your agent drives the browser from its E2B sandbox with a few CLI commands, and you can watch every session live or step in when it gets stuck.
In the cookbook example, an agent serves an app from its E2B sandbox, then a Notte browser opens it, adds a to-do, and confirms the result.
Cookbook: github.com/e2b-dev/e2b-cookb…
Docs: docs.notte.cc/integrations/e…
ALT New E2B integrations: veris and notte
Ladies and gentlemen, You can now use @nottecore browsers inside @boatdotdev sandboxes ⛵️
→ Run your agent harness in boat sandboxes
→ Spawns 100s of ultrafast browsers with Notte CLI
→ Agent can access any site with best in class stealth
→ Keep browser stuff off your VM RAM and CPU
Your agent runs in boat. Its browsers run on Notte. 🫡
Let your agent test the app it just built, or automate websites from inside the sandbox. Use Notte CLI directly from your agent, or control the browser with Python + Playwright. Get started: docs.notte.cc/integrations/b…
Your logins, now secured in the cloud.
Your agent's cloud browser is stuck at a login wall. Your own browser is already signed in. One command copies those logins to Notte:
→ notte profiles sync
→ Chrome, Firefox, Arc, Brave, Edge, Helium, Chromium
→ pick exactly which sites with --domain
→ nothing leaves your Mac until you say yes
Every session now starts signed in.
Try it now!
Docs: docs.notte.cc/cli-reference/…
Or ask your agent: notte.cc/skill.md
Notte is now fully Enterprise-ready
Enterprise customers kept asking for the same things before rolling out browsers to their agents. They're live:
→ SAML SSO with Okta, Entra ID, Google Workspace
→ SCIM: add someone in your IdP and they're in
→ Audit logs, with CSV export and API access
Want SSO for your org? Reach out at [email protected]
SOC 2 Type II, security docs and policies: trust.notte.cc
Audit events API: docs.notte.cc/api-reference/…
Dump this to your favorite AI agent:
docs.notte.cc/cli-reference
