Anything API - Any website. We deliver the API.
by•
Many websites don't have public APIs. Anything API fills that gap.
Turn any browser work into a production-ready API. Describe the task, and our agents build a custom function that calls the site directly. Ship a custom API endpoint you can deploy serverless, schedule on Cron, or call via API.
Tell Notte what you need. We ship the function endpoint.
Replies
Notte
@chriswyatt2 good question - to generate the API you'd need to run the automation in a browser session first, handle the browser infra, captchas, proxies, auth etc. Anything API uses the Notte CLI to generate the browser session and ships it as an endpoint (that you can deploy serverless, schedule on cron, call via API)
Notte
@chriswyatt2 Yeah as Sam said, main diff is the hosted service. You can run your claude code generate API so many times locally but if you need to run it at scale or when you sleep you better have a managed infra that also handles stealth with your volume
Notte
Hey PH 👋
We're the team behind Notte, a browser automation platform, and today we're launching Anything API!
Most websites don't have public APIs. If you want the data or the workflow, someone has to build and maintain the automation. Anything API handles that for you.
Describe what you need done in the browser, our agent uses the Notte CLI to execute it, build the workflow, and ship a callable function endpoint. Deploy it serverless, schedule on Cron, or call it via API. No setup or infra to manage.
Who it's for:
🔁 Teams running the same browser workflows repeatedly
📦 Developers who need data from sites with no public API
⚙️ Anyone automating anything, from document processing to form submissions to data extraction
Try it free at: anything.notte.cc
We'd love to know - what site or workflow would you point this at?
@ogandreakiro Does this scrape the website to get the data and expose as an API ? I did not understand "Developers who need data from sites with no public API"
Great question — yes, it looks like they’re using browser automation to execute the flow on the target site, then exposing the result as a callable endpoint. The useful part for GTM/sales teams is you can automate repetitive portal workflows (pricing checks, lead enrichment lookups, form pulls) without waiting for a first-party API. Curious @ogandreakiro: do you support anti-bot/session handling out of the box, or should teams wire that separately?
Notte
@danielsinewe Yes we do support all of the stealth support out of the box through Notte
Love that — that’s the missing piece for most teams. A useful next layer could be a reliability contract per endpoint: expected output schema + confidence score + auto-fallback (retry/screenshot/manual queue) when the site shifts. That would make this production-safe for sales/ops workflows, not just demos.
Notte
@ambikaiyer29 Yes, you could for instance ask Anything agent to build an API endpoint to scrape data. Anything does need the website you want to interact with to expose APIs to still be able to retrieve the data or perform the flow you you've asked for
What about bypassing bot blocking? For example, if I need to get content from an e-commerce site and they don’t have an API. Such sites usually ban bots. Do you bypass that?
Notte
@mykyta_semenov_ Anything is compatible with all stealth options you get in Notte (Residential proxies, captcha solving, etc.) but we enforce fair use policy so Anything will not let you bypass websites terms of use
Product Hunt
Notte
@curiouskitty yes we do. We leverage the full notte ecosystem (browser profiles, vaults, etc.) to build the automation
Notte
@curiouskitty for auth flows that require 2FA, we recommend using browser profiles and either login manually to persist the cookies, or use an Agent to login on your behalf. If you put your MFA secret inside our vaults, the agent can login super easily
@curiouskitty Turning any website workflow into an API feels like a really powerful abstraction. A lot of automation tools still struggle with the messy parts of real-world browser interaction like logins, session state, and authentication changes.
Having agents generate production-ready endpoints on top of those flows could unlock a lot of integrations that normally require custom scraping or brittle scripts.
Curious what kinds of workflows people are building most often so far.
I just used this for my platform One Pager and I gotta say wow!
This is much more than a standard chatbot.
One Pager rapidly creates websites for outreach, but does not have a public API at the moment. I entered my website, then anything API created an account, logged in starting understanding my platform and created an API to build website using my data structure.
This is something I haven't seen before and really impressed me.
Curios if there is a way to output the endpoints created into a document for external use?
Also how to you ensure that people aren't building APIs for sites that aren't theirs?
Notte
@jake_friedberg Re security - we're trying to enforce as much as possible a fair use policy through our agent prompt and safety railguard. Eg - Anything will not let you automate LinkedIn work due to their terms of services
Notte
@jake_friedberg hey Jake! thanks for the nice feedback. Yes the endpoint that gets created is actually hosted as a Notte function on Notte (You get a pointer to the Notte console from Anything). You can get the curl command to invoke the function from anywhere directly from the Notte console and also get observability and co from there. hope this helps?
Velocity: AI User testing
Kind of amazing that you can generate an API like this. Does it suffer from the same problems as web scrapers if the DOM should change dynamically? Since it's an API I'm supposing that actually it could protect as a layer of abstraction above the changes on the page and then you just get it to self heal on a recurring basis? Perhaps you could even charge for that self healing cadence.
Notte
@kevin_mcdonagh1 Yes exactly, Anything tries to do as much as possible at the API level (faster, more stable, etc.) when it's not possible to do so the Anything agent is also able to generate script that themselves use playwright and browser agents; so you end up with hybrid browser functions. If your usecase only leverage APIs than its much less sensitive to UI changes, if it's hybrid it will be a bit more. We're working on self-healing as a next step
This solves a real pain — so many useful sites still have no API. Turning browser workflows into callable endpoints could save teams a lot of brittle scraping work. Curious how it handles sites that change their UI often.
Notte
@allinonetools_net once the endpoint is built, subsequent runs call the site directly rather than re-navigating the browser UI, so UI changes don’t affect it after the initial build
Notte
@allinonetools_net Handling function rebuilds on sites updates will be our next move ;)
This is pretty cool. Btw when the agent generates the API endpoint, how deterministic is the execution layer? Is the AI only used during the build phase and the runtime stays fully scripted?
Notte
@lak7 The AI tries its best to create a fully scripted runtime, but can also create hybrids where an AI agent itself can be used during the execution of the function if needed
Hey launch team, congrats on the launch!
This is a great idea for creating quick production grade API's. I can't wait to try it out, the interface looks very clean and easy to use as well. I particularly like the "what it does" section but would it perhaps be a bit more helpful to have a hovering "alt-text" when a user hovers over a function / curl command for more ease of use to explain what each element does, this would also help users be more confident in reducing bloatware.
Hunter @garrytan coming in clutch with these new product launches! XD
Notte
@garrytan @minhajulll let us know what you think once you've tried it! also the "alt-text" thought is a good idea thanks 😇
Notte
@garrytan @minhajulll Thanks for the suggestion Mj!
Inspector
This is so cool!
Notte
@mklikushin glad you think so too:)
Notte
@mklikushin Gracias 🙏🏻