keychains.dev
Hi HN — I’m a heavy OpenClaw user and, like many others, I’ve been thinking about how to give these new “unleashed” agents secure access to my accounts. Agents need API access to be useful. But API keys are long-lived secrets. And agents are not secure environments. So I built something for myself that quickly turned into a product: keychains.dev. The idea is simple: agents never see raw credentials. With Keychains.dev: • Agents make API calls via a drop-in replacement for curl or JavaScript’s fetch() • They use template variable names instead of embedding credentials • The request is…
keychains.dev launched on February 20, 2026 with 177 votes, #168 of 16,628 launches that month and more than 99% of that year's launches.
What it does
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).
Let your AI agents access any API without leaking sensitive credentials. SSH-secured, user-controlled, revocable permissions for the agentic web.
Let AI agents access any API without leaking sensitive credentials. Users stay in control. Permissions are scoped, transparent, and revocable. Your agent gets exactly the access it needs — nothing more. Your users decide what to share, and can revoke it anytime. Use keychains curl as a drop-in replacement for curl . The only difference: replace hard-coded credentials with template variables like {{OAUTH2_ACCESS_TOKEN}} or {{STRIPE_PRIVATE_KEY}} . When a new API scope is needed, the user sees exactly what the agent wants to do and approves with one click. Keychains injects the right credentials server-side. Your agent never sees the raw secrets — invisible to prompt injection. Built from the…from keychains.dev
In the maker’s words, at launch
Hi HN — I’m a heavy OpenClaw user and, like many others, I’ve been thinking about how to give these new “unleashed” agents secure access to my accounts. Agents need API access to be useful. But API keys are long-lived secrets. And agents are not secure environments. So I built something for myself that quickly turned…
Does a similar job
all alternatives →
OneCLI – Vault for AI Agents in RustMar 2026 · github.com · ▲161We built OneCLI because AI agents are being given raw API keys. And it's going about as well as you'd expect. We figured the answer isn't "don't give agents access," it's "give them access without giving them secrets." OneCLI is an open-source gateway that sits between your AI agents and the services they call. You store your real credentials once in OneCLI's encrypted vault, and give your agents placeholder keys. When an agent makes an HTTP call through the proxy, OneCLI matches the request by host/path, verifies the agent should have access, swaps the placeholder for the real…
I built an open source computer-use SDK enabling agents to authenticate2025 · github.com · ▲19over this weekend myself and two of my friends took part in a hackathon and built this side-project. we have been diving into computer-use recently and developed an sdk to make it easy to implement for devs like us. one feature we were missing though, was the agent being able to log into services. anthropic understandably blocks this capability with their guardrails, and you wouldn't want your credentials to end up in any model context anyways. so we added a keychain service to the vm that the agent is using. it was built using the pass cli (https://www.passwordstore.org/).…
LatchkeyMar 2026 · github.com · ▲122Hi HN, At Imbue, we’ve been following the rapid developments in the agent landscape and noticed that the way agents interact with third-party services on users’ behalf often leaves a lot to be desired. Integrations are ad hoc, complicated, context-heavy, and either unfriendly to non-technical users or tied to a lock-in of some sort. We‘re experimenting with a command-line tool, Latchkey, that could be used by local agents targeted at non-technical users while avoiding remote intermediaries. As far as we know, this is the only existing approach at the intersection of these two goals. Core…
OAuth for AI Agents2025 · github.com · ▲8I’ve been experimenting with AI agents lately, and one problem kept coming up: they either get a raw API key with full access or nothing at all. That’s risky, especially if you’re testing agents that can make arbitrary calls. So I hacked together a tiny package called Kage Keys - https://github.com/kagehq/keys It lets you wrap agent actions with scoped, short-lived tokens instead of handing over your real API keys. Example: ```js import { withAgentKey, getLogs } from "@kagehq/keys"; async function main() { await withAgentKey("github:repos.read", async () => {…
More ai this month
the category →
Paintings by AI models: programs run through a simulation of oil paint.
AI · 20d ago · stillwet.art
PixVerse R2▲381A real-time world model you can explore and change
AI · 28d ago · world.pixverse.video
Source: Product Hunt launch ↗ · launch text quoted in part
Launched alongside, February 2026
the whole month →
Lovon AI Therapy▲801Feel closer and have more fun with your partner every day!
AI · Feb 2026 · lovon.app
Hello my name is Ben Ward for the past 3 years I have been remastering the financial game Wall Street Raider created by Michael Jenkins originally on DOS in 1986. It has been a rough journey but I finally see the light at the end of the tunnel. I just recently redid the website and thought maybe the full story of how this project came to be would interest you all. Thank you for reading.
Work · Feb 2026 · wallstreetraider.com