Hacker News new | ask | show | jobs
by throw03172019 13 days ago
How are you all different than the other few CUA APIs in this batch and previous batches?
3 comments

We don't just provide end-to-end API, we're a SOTA harness where you can bring in your own OpenAI or Claude keys and run it on and also we're the only modular API in the market - we give you the ability to control any part of CUA and charge by the type of call as you can see in https://coasty.ai/docs.
What do you think that makes your solution "SOTA"? That's quite the interesting claim, which is obviously false.
We've hit 82.8% on OSWorld Verfied(on the official page) and with our latest internal testing we're hitting 85.6% which we've posted (https://github.com/coasty-ai/coasty-osworld).
That’s really nice actually. Do the screenshots and playback and logs get stored on our systems as well?
Yes, you have access to all your logs and screenshots and playback!
Sure but is that stored on our infra or yours? (Work in HIPAA regulated industry)
We're SOC2 and HIPAA compliant and have zero data retention policies through our enterprise platform where it's all covered and we don't keep any data that you don't want us to!
With our API, you can also create a very customizable blend of deterministic workflows and AI calls for CUA, so for example, Coasty for recovery can kick in when something unexpected like a dialog box or popup happens during your deterministic workflow runs.
"Zapier to monitor email inbox and then extract the code" - I hit this exact wall, and ended up building the missing piece myself. The agent gets its own managed address on our domain, and one call blocks until the verification email arrives and it is automatically parsed for OTPs/code/magic link. Available at https://sente.run/