Viktor.comAn AI coworker that actually does the work
keychains.dev
Give AI access to 6754+ APIs with zero credentials exposed
289 followers
Give AI access to 6754+ APIs with zero credentials exposed
289 followers
Keychains.dev is a secure credential proxy for AI agents. Use "keychains curl" as a drop-in for curl — just replace hard-coded credentials with template variables like {{GITHUB_TOKEN}}. Keychains injects real credentials server-side. Your agent never sees raw secrets — immune to prompt injection by design. Users approve each permission with one click and can revoke access anytime. Full audit trail. Works with 11,000+ API providers (OAuth, API keys, basic auth).
Sketchfab
@albn Hi Alban, this tackles one of the biggest blockers for agent adoption. Giving agents raw API keys has always felt like crossing a line.
Injecting credentials server side while keeping them out of the agent’s context is a smart trust layer. This makes real world agent workflows much more viable.
I’m building Ahsk app , a macOS AI assistant focused on secure, in flow AI use. Would love to connect and exchange feedback.
Product Hunt
keychains.dev
@curiouskitty That's a great question. Got the same feedback from a few users past Wednesday. What I did for now is that I split the credentials pipeline from the data pipeline and open sourced the proxy so you can deploy your own proxy as a user. I called it "Satellite proxy" --> you host your own copy of our proxy on Vercel, it's the only one seeing request bodies and response data, and it calls keychains.dev only to resolve credentials.
I imagine I could do the same kind of trick to let you store your own API keys (except OAuth) so they never touch our servers.
If you have better ideas on this I'd love to implement them!
keychains.dev
This is a great idea. Have you thought about expanding it to also support traditional website passwords, so agents couldn’t access those either? Curious whether you see this eventually replacing tools like 1Password, or staying focused purely on developer/API secrets.
keychains.dev
@bricohen I'd love to do websites passwords. A bit more tricky though.
IMHO the next step could be to offer website owners a SDK as simple to use as Clerk (and if possible, compatible) to offer safe agent-oriented login in browser --> would love to work on that!
Credential handling in AI agents is one of those things that looks fine in demos but breaks fast in prod. I've seen raw API keys just float through context windows more times than I'd like to admit. The prompt injection immunity part is what I find most interesting here - you can't inject what the model never had access to. Curious how you handle OAuth token refresh mid-task though? If a token expires while an agent is running a long job, does it just get a 401 or is there auto-refresh built in?
keychains.dev
Great tool! Though we could use some more guidance on how to setup for Shopify App OAUTH now that Shopify has deprecated static admin API keys in favor of temporary keys based on Client ID and Client Secret. Spent quite a long time playing around with it and best we can figure out we are either doing something wrong or Keychains is hardwired to use the old Shopify API key auth method. We ended up building a workaround wrapper for our worker to use, but would be nicer to have this work directly in Keychains! Appreciate any help you could provide and happy to provide more details on the Shopify use case if you need it. https://shopify.dev/docs/apps/build/authentication-authorization/client-secrets
keychains.dev
Hey @ian_rothfuss ,
Thanks for the feedback. Will look into it asap
Buildrs
Nice product ! Keep building
keychains.dev
@dagher_jade Thanks!
Tugan.ai
good luck with your launch ! @severin__
keychains.dev
Thank you @baptiste1 !