am03

Amazon does work! It's actually one of our most used tools. We have a custom stealth stack consisting of things like in-house CAPTCHA solvers, cloud browsers, custom IPs, and adjustments to playwright that help us with matching normal web traffic.

Would recommend you try it out, seeing is believing

We have a lot of car dealership users actually! We have a custom stealth stack in our free hosted version that addresses some of the more complex anti-bot elements, including in-house CAPTCHA solvers, custom Chromium adjustments, etc. Generally when we have repairs those have to do with site changes moreso than anti-bot itself.

Curious if there are any particular sites you've had trouble with!

We're seeing about a 2.2% error rate on runs, and 82% of those errors get automatically resolved by our repair agents currently. The highest failure rates seem to come on travel and automotive marketplaces, as they tend to have more complex interfaces. By contrast we have near-zero error rates on retail.

Yep Linkedin is very touchy. We don't have support yet, but something we're thinking about! Our top priority is making sure people don't get banned.

We have some provisional support for signing into Google oauth on sites if that's what you mean! Still in beta though. Our MCPs themselves also have an oauth option.

Of course, there's nothing preventing anyone from trying this idea as well, but to us it's a fairly different approach to browser use. There's some additional infrastructure around managing anti-bot and things like that which bigger companies seem more hesitant to do. The token savings also cut fairly strongly into their existing margins.

Printing Press is a great project! At a philosophical level, Pomerado is meant to be more autonomous - it's a standalone harness that you can run, and it's meant to require as little review as possible after the first request. If there are questions about the site or intent, we have coding agents with application context answer those questions.

We find this integrates into automated software development workflows a lot better, and my Openclaw can basically create new MCPs for me with little supervision required.

In terms of mechanisms, Pomerado uses a mix of HTTP requests and generated Playwright code. Printing Press has a far greater emphasis on making HTTP requests to the site's backend. We've found for some sites this latter approach can create issues around triggering anti-bot and can fail for more complicated forms and writes, so we use Playwright for those instances.

Pomerado's approach to researching the website is also a bit different - we solely focus on exploring the website itself, while Printing Press has your agent explore the web for documentation, SDKs, etc. There's a tradeoff of prompt injection security vs convenience there. Because we try to emphasize autonomous builds we limit the agent to the website for security.

A big pain point for us with existing approaches was using them for cloud agents (e.g., my Openclaw on my VPS). Cloud starts running into a lot of issues around hosting, authentication, and anti-bot, which is why we started offering a free hosted version of the open source, where we handle cloud browsers, proxy rotation, credential storage, CAPTCHAs, etc.

We're planning to roll out support for CLIs down the line! And the PR for non-OpenAI models + codex exec is in the works :)