I cant find any information on models you support?
Show HN: Steel.dev – An open-source browser API for AI agents and apps
21–30 of 53 posts
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#22Can you say more about your product plans? It looks like this is directly competing with Browserbase — how will you differentiate? Looking forward to seeing how the product and company grows
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#23Happy to see there's a way to get browser automation for AI without building infrastructure to support it. Yet I don't see examples of connecting an LLM to drive a web session, just examples of using Puppeteer or Playwright or Selenium to drive a web session. Presumably your user base knows how to write custom code for an interface between Claude or OpenAI API and Puppeteer/Playwright/Selenium. Sadly, I don't know how to do that. Would it be fair to expect your documentation to help? What would you suggest to get started?
Is the interface between Steel, or Puppeteer/Playwright/Selenium, something that might be implemented in the new Anthropic Model Context Protocol, so there's less custom code required?
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#24Very interesting. I worry that if I use your cloud, and a lot of other people do, all of your IP addresses will get banned by all the big players. It will definitely be a fun cat and mouse game! Related story: Way back in the day, PayPal was just getting started, and decided eBay transactions would be their perfect customer. The only problem is that eBay didn't allow scraping. So they built an entire proxy infrastruc…
That honestly sounds so fun! Who better to build your defences than your attackers ahaha Tying into your concern, keeping IPs fresh and high quality will definitely be a balancing act as we get bigger. It'd be one today too if we were to try to offer super granular location controls because there's only so many proxies in X state, let alone X city. Currently, we get to aggregate & QA from multiple proxy providers, so…
you might have a captcha issue on your discord haha or something, I cannot join
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#25Very interesting. I worry that if I use your cloud, and a lot of other people do, all of your IP addresses will get banned by all the big players. It will definitely be a fun cat and mouse game! Related story: Way back in the day, PayPal was just getting started, and decided eBay transactions would be their perfect customer. The only problem is that eBay didn't allow scraping. So they built an entire proxy infrastruc…
That honestly sounds so fun! Who better to build your defences than your attackers ahaha Tying into your concern, keeping IPs fresh and high quality will definitely be a balancing act as we get bigger. It'd be one today too if we were to try to offer super granular location controls because there's only so many proxies in X state, let alone X city. Currently, we get to aggregate & QA from multiple proxy providers, so…
Is it possible to persist an IP address if we supply the proxy credentials?
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#26Hello Hacker News! We’re Nas and Huss, co-founders of steel.dev ( http://steel.dev ). Steel is an open-source browser API for AI agents and apps. We make it easy for AI devs to build browser automation into their products without getting flagged as a bot or worrying about browser infra. over the last year or so, we’ve built quite a few AI apps that interact with the web and noticed - a. it was magical when you could…
Would love to read an engineering blog about your journey from trying to run this on Kubernetes and ending up on Firecracker VM.
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#27Why not a browser extension?
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#28I don't understand what problem you're solving that puppeteer doesn't already solve.
We love Puppeteer and use it to power our API! We don't compete with Puppeteer/Playwright/Selenium but we're focused on solving the problem of hosting Chromium browsers in the cloud. The workflow jump we've seen ourselves and from customers is that it's pretty straightforward to build these scripts locally, but the moment you want to run them in prod, you now need to deal with a ton of overhead around packaging up to…
And why run in the cloud in place of my own computer, with my own IP that won't be flagged for being an AWS IP?
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#29Very interesting. I worry that if I use your cloud, and a lot of other people do, all of your IP addresses will get banned by all the big players. It will definitely be a fun cat and mouse game! Related story: Way back in the day, PayPal was just getting started, and decided eBay transactions would be their perfect customer. The only problem is that eBay didn't allow scraping. So they built an entire proxy infrastruc…
That honestly sounds so fun! Who better to build your defences than your attackers ahaha Tying into your concern, keeping IPs fresh and high quality will definitely be a balancing act as we get bigger. It'd be one today too if we were to try to offer super granular location controls because there's only so many proxies in X state, let alone X city. Currently, we get to aggregate & QA from multiple proxy providers, so…
+1 to residential proxy providers like joinmassive.com ! #proudinvestor
Re: Show HN: Steel.dev – An open-source browser API for AI agents and apps
#30Can this defeat perimeterX used by Zillow?