Launched this week
**Product Hunt: Claim $5 at zero.xyz, the free power tool for AI agents** Zero unblocks your agents so they can discover services to accomplish tasks, no APIs keys or config. Works with Claude Code, Codex, Gemini, OpenClaw, Hermes and most other CLI agents. Make your agents better with Zero.













The API key friction is real — anyone building with AI agents spends a lot of time on config vs actual building. Curious how this handles auth for services that require OAuth flows — is that abstracted away too, or does the user still need to handle that manually?
zero.xyz
@richard_pierre_reid services that require OAuth flow aren't generally among the around 8000 services currently indexed on the platform because of their transactional nature. Did you have something in mind? Thanks for the comment!
@michael_ludden sorry for the delayed reply! Thanks for clarifying — that makes sense given the transactional complexity of OAuth flows. No specific service in mind right now, more curious about the boundaries of what's abstracted. Impressive scope at 8,000 services regardless. Will give it a proper try. Wishing you all the best with zero.xyz!
zero.xyz
@richard_pierre_reid please do, and thank you! all the best to you too!
Curious about the auth layer here — most of the 8k tools fit a key-or-OAuth model, but the payment and fintech ones (Stripe, Plaid, Bridge, Privy) typically require per-merchant tokens or end-user consent flows that don't proxy cleanly. Do you support that subset, or is the catalog more read/info-side for now?
zero.xyz
@sweepbase can you give an example of what you mean? I'm not sure I'm grokking the question. For example, Stripe is the creator of MPP (alongside Tempo, which they own), and half the services indexed via Zero are MPP, the other half being x402 at the moment.
Love the tool discovery focus—how do you prevent tool sprawl and conflicts when agents suddenly have access to thousands of tools?
zero.xyz
@leventbuilds great question, and that's EXACTLY what Zero does! It's a search tool for services that exist (currently) on MPP or x402 protocols. We stack rank them based on a whole host of robust metadata collected from previous runs, including % success rate, speed, price, quality, number of transactions, time on platform etcetera - then we present the options to the agent so that it is able to choose a high quality solution to execute on behalf of the user. You can browse a list of the services with all kinds of data about them from previous runs, and the proviter itself, here: https://zero.xyz/browse
The tool discovery layer without requiring per-service API key config is the hard part. Most agent frameworks make you wire up each integration manually. We've hit exactly this friction building AI workflows where adding a new data source means plumbing OAuth differently every time. How does zero handle auth token refresh and rate limit management across 4k services at scale?
zero.xyz
@retain_dev no auth required. check it out and let us know what you think! It's free, heh.
Mindra
Hey team,
Congrats on the launch. I wonder how these agents handle oauth, or other authentication problems
zero.xyz
@zeynep_yorulmaz no authentication necessary! transactions only - your agent goes and finds a service, we show the top ranked results based on a bunch of previous agent reviews, runs and other metrics and your agent chooses a service it thinks will do the job you told it to, transacts, and the result is delivered to your agent. transaction done - no auth necessary.
Interesting wedge. The setup friction is real, but the next trust layer is admission control once agents can actually spend. We keep seeing runs look productive while they retry the same failure class. Curious whether you plan to expose native spend receipts, pause rules, or verifier hooks at the platform layer, or whether you want that to live entirely in the calling agent. We are thinking about the control-plane side of the same problem at MartinLoop, so I am following this closely.
zero.xyz
@keesan12 great thoughts and insights. yes, setup friction is real right now, as you might expect for an early, bleeding edge offering like this. and yes we're certainly thinking about a lot of future directions here, but curious what you meant by "We keep seeing runs look productive while they retry the same failure class" - did you mean using Zero? Would love to understand more! Could be very valuable feedback, ty
mailX by mailwarm
What kinds of services can agents actually discover through Zero right now?
zero.xyz
@othman_katim here's the full list of almost 8000, but TL;DR a crazy diversity of services. web domain hosting, physical postcard sending, image generation, video editing, song creation - all sorts of stuff. check it out! https://www.zero.xyz/browse