Tabstack Browser Automation

Automate the web in your app or agent, no browser to host

API

Developer Tools

Artificial Intelligence

Visit WebsiteSee on Product Hunt

Being able to just type '/automate' and dictate what I want to be done is an incredible UX. I'm going to explore hooking this up to my own agents today!

Congrats on #3! What’s been the hardest part of building reliable browser automation for AI agents?

Not having to host the browser removes the exact part of web automation that always breaks in production. How are you handling sites with heavy bot detection, is that abstracted away or still on the developer side? Reading the accessibility tree instead of screenshots is a smart cost move too, that token math adds up fast at scale.

Mozilla shipping something this developer-focused and privacy-conscious feels like a nice return to form. Loving that robots.txt compliance and ephemeral processing are defaults, not afterthoughts.

Schema-defined extraction is the bit I was missing, and it worked cleanly on a couple of messy product pages. The robots.txt compliance and no-training stance from Mozilla make it easy to ship without a long legal check.

How does the pricing scale if my agent is firing hundreds of these calls per hour, and is there a way to cap costs before things get out of hand?

the stateless-per-call design makes sense for reliability but I'm curious how it handles flows that need to stay logged in across steps - like a site where you need a session cookie from step one to do anything in step two. do you pass auth state back in yourself each call, or is there something built in for that

How does the ephemeral processing actually work in practice, like is there any retention window for debugging failed calls or is it truly gone the second the response lands?

How does the pricing actually work for the research calls versus the simpler Markdown or extraction endpoints, since those seem like pretty different workloads?

finally tried this and the schema extraction felt shockingly clean, called it for a few messy product pages and got structured JSON back without babysitting.

Curious how it handles sites that block headless browsers or rely heavily on client-side rendering since you mentioned no browser infra on my end.

The robots.txt compliance baked in by default is a really thoughtful touch, especially from Mozilla. Feels like they actually thought through the trust layer for devs shipping agents, not just the shiny API surface.

Mozilla backing this is what got me to try it, and the schema extraction actually nailed a messy product page on the first try. Glad my data isn't getting fed into some training pipeline either.

Finally tried Tabstack and the schema-defined extraction is genuinely useful, no more wrestling with messy scraped HTML. Love that robots.txt and ephemeral processing come baked in by default.

Spent a few minutes poking around the schema extraction and it actually nailed a messy recipe page on the first try. The robots.txt compliance detail is a nice touch for anyone tired of sketchy scrapers.

How does this handle sites with heavy bot protection or JS-only content that needs real browser interaction, and is that tier priced differently than simple fetches?

how does the robots.txt compliance work when an agent needs data from a page that's blocked but technically accessible via the rendered DOM?

Tried it on a couple research queries and the cited multi-source output was solid. Nice that it returns clean Markdown instead of forcing me to parse raw HTML.

how does the robots.txt compliance actually work when an agent needs to interact with a page that blocks scraping, does the API just refuse or is there a way to get the structured data another way