Garry Tan

Anything API - Any website. We deliver the API.

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.

Add a comment

Replies

Best
Gabriel Abi Ramia

This is solving a real pain point. Building API integrations from scratch for every data source is exhausting — I've been through it connecting YouTube, Stripe, and multiple AI providers for my SaaS. How are you handling rate limits and auth differences across platforms? That's always been the hardest part for us.

Andrea Pinto

@aitubespark Rate limits really depends on the site you automate, ideally you wouldn't have any. Auth can be managed with all the Notte services we have (session profiles, agent vaults, etc.)

Brianna Lin

This is rlly interesting! Just curious -- how do you decide when the agent should rely on the scripted workflow vs switching to AI reasoning if something unexpected happens on the page? 👀

Andrea Pinto

@brianna_lin That all happens at build time, once the agent deploys the function its supposed to work. A few weeks later if theres a massive site UI change or API change it might break, but we're working on managed self-healing to handle this in the background for users out of the box

Arjun Chintapalli

Cool stuff!

Couple of questions:
1. What happens when the site's API's/layout changes? Is this just going to silently fail with 0 results?
2. So after creating the API is it still going to launch a browser and so this just a playwright script getting executed or is your agent writing a script to hit the underlying API's of the site?


Andrea Pinto

@arjun_chintapalli Thanks Arjun! 1) For now the function would just return an error when you'll invoke it, so would fail if there's a massive API/layout change but not silently. 2) The idea is to avoid spinning up a browser as much as possible - this is the case when our agent found a 100% API path, otherwise it creates a hybrid flow, in that case we still use our session browsers.

Arjun Chintapalli

@ogandreakiro I have done this kind of scraping by just manually looking at the network requests in Inspector, pasting requests into Claude and Claude just wrote and executed a script and gave me the data for free.

Would this be the comparable for this?

Andrea Pinto

@arjun_chintapalli Anything does that in the 1st place, but then also (and that's the main value prop) lets you run your job (scraping or automation) at scale concurrently 24/7 - which ppl would struggle to do on their local machine, or with home rolled browser infra

LBan

Love the value prop — super clear. Which website types are currently the hardest to normalize into stable API outputs (e.g., dynamic pages, auth walls, anti-bot pages)?

Andrea Pinto

@hanxl Thanks! For now its a bit hard to say, we need to analyze all the traces we got :)

John Rush

My favorite browser use API

Been using it for my web agents for a long while . E.g. for Listingbott.com

Sam Morris

@johnrushx 🤜🤛

Andrea Pinto

@johnrushx Thanks John!

Winston

When should a company use Anything API instead of building internal browser automation with Playwright?

Sam Morris

@winstonqian Playwright gives you the browser control layer but you still have to build everything around it: cloud execution, scaling, proxy rotation, auth handling, scheduling, and fixing breakages when sites change (we use it for hybrid workflows, merging agent + playwright for increased playwright reliability).


Use Anything API when you want the endpoint and all the infra managed for you, which makes it much easier to scale (we do it for for you).

Irosha de Silva

The hybrid approach of deterministic scripts plus AI reasoning sounds like a game-changer for stability.

How does the system decide when to hand off a task from a script to the AI agent during execution?

Andrea Pinto

@iroshads thanks Irosha! Handoff only happens when an issue occurs, otherwise all is predefined

Dane Walters
This is a really interesting idea. One thing I’ve noticed building platforms that rely heavily on APIs is that many services don’t provide endpoints for things like product previews, catalog interactions, or storefront workflows. Tools like this could be extremely useful for automating tasks across sites that were never designed with developer integrations in mind. Curious how you handle authentication flows, rate limiting, and dynamic pages where the DOM changes frequently?
Andrea Pinto

@dane_walters Yep, that's the entire unlock value! Auth works either with your own credentials, or letting the agent create its own accounts where he needs to. If Anything agent worked well and the output browser function leverages only API calls, DOM changes are less a problem for the script reliability

Haroon Haneef
wonderfull product, tested it to track parcel with dynamic values, it's great what about the pricing?
Andrea Pinto

@haroon_haneef thanks! Much appreciated. Around launch time we decided generation would be free for early users. But we'll become pay for the tokens you use (no markup on our side) and then pay for the browser sessions & functions infra when you schedule and scale your jobs. Pricing is v competitive: https://www.notte.cc/#pricing

Aarush Mishra
Any website will need authentication to perform a task, and the bot asks me to type my email id and password to perform this task, how can I trust a bot and give my credentials? Atleast for any login I have trust of google auth but in this case the bot asks to type email and password, how is that helpful
Andrea Pinto

@aarush_mishra Would you feel safer if you'd one click integrate with 1password? (not writing down the credentials to the bot)