AI · alternatives · 2026
24 alternatives to Cred
OAuth credential delegation for AI agents
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Hey HN! Today we're launching Agent Vault - an open source HTTP credential proxy and vault for AI agents. Repo is at https://github.com/Infisical/agent-vault, and there's an in-depth description at https://infisical.com/blog/agent-vault-the-open-source-crede.... We built Agent Vault in response to a question that been plaguing the industry: How do we give agents secure access to services without them reading any secrets? Most teams building agents have run into this exact problem: They build an agent or agentic system and come to realize at some point…
Apr 2026 · github.com · its alternatives →
- 2KD
Every AI agent that does something useful - opening a PR, posting in Slack, updating a ticket - needs to call an API on behalf of a user. That means OAuth. Authorization flows, token storage, refresh logic, per-user credential isolation. Today, most teams solve this with a long-lived API key in an .env file, shared across every user and every session. As everyone in an organization becomes a software engineer - whether they know it or not - you can't expect each of them to roll their own OAuth. Secure credential handling needs to be baked into the infrastructure. The core issue: agents are a…
Mar 2026 · kontext.dev · its alternatives →
- 3
We built the Kontext CLI because AI coding agents need access to GitHub, Stripe, databases, and dozens of other services — and right now most teams handle this by copy-pasting long-lived API keys into .env files, or the actual chat interface, whilst hoping for the best. The problem isn't just secret sprawl. It's that there's no lineage of access. You don't know which developer launched which agent, what it accessed, or whether it should have been allowed to. The moment you hand raw credentials to a process, you've lost the ability to enforce policy, audit access, or rotate without pain. The…
Apr 2026 · github.com · its alternatives →
- 4
keychains.dev▲177Hi 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…
Feb 2026 · keychains.dev · its alternatives →
- 5
- 6
DCP▲104Give your AI agents encrypted permission and keys
May 2026 · dcpagent.com · its alternatives →
- 7
- 8
- 9
OneCLI▲143Give every employee a secured, sandboxed pro assistant agent
Aug 2026 · onecli.sh · its alternatives →
- 10
We 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…
Mar 2026 · github.com · its alternatives →
- 11
Latchkey▲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…
Mar 2026 · github.com · its alternatives →
- 12
NervePay▲74Give AI agents identity, secrets vault & analytics
Feb 2026 · nervepay.xyz · its alternatives →
- 13
over 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/).…
2025 · github.com · its alternatives →
- 14
HelixID▲34Open-source identity & trust layer for AI agents
Sep 2026 · helixid.dev · its alternatives →
- 15
- 16
Hi HN, I built Agent Passport, an open-source identity verification layer for AI agents. Think "Sign in with Google, but for Agents." The problem: AI agents are everywhere now (OpenClaw has 180K+ GitHub stars, Moltbook had 2.3M agent accounts), but there's no standard way for agents to prove their identity. Malicious agents can impersonate others, and skill/plugin marketplaces have no auth layer. Cisco's security team already found data exfiltration in third-party agent skills. Agent Passport solves this with: - Ed25519 challenge-response authentication (private keys never leave the…
Feb 2026 · agent-passport-red.vercel.app · its alternatives →
- 17
- 18
MachineAuth is a self-hosted OAuth 2.0 server for authenticating AI agents and machines. What is an AI agent in this context? A software bot (like OpenCLAW, Claude Code, etc.) that makes API calls to access protected resources. Instead of sharing long-lived API keys, your agents can authenticate using OAuth 2.0 Client Credentials and receive short-lived JWT tokens. Why? No more sharing API keys Short-lived tokens (configurable) Easy credential rotation Industry-standard security
Feb 2026 · github.com · its alternatives →
- 19
Token efficient IDs for AI agents. UUID alternative for the agentic era. - vostride/id-agent
May 2026 · github.com · its alternatives →
- 20
Share API keys with AI agents. Encrypted. No server needed.
Feb 2026 · its alternatives →
- 21
Authorizer▲21Open-source auth for enterprise applications, and AI agents
Sep 2026 · authorizer.dev · its alternatives →
- 22
I’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 () => {…
2025 · github.com · its alternatives →
- 23
Identity and trust for AI agents — verify, revoke, enforce
Mar 2026 · agentspassports.com · its alternatives →
- 24
Fullmakt▲1Scoped, revocable credentials for AI agents — fully audited
Aug 2026 · fullmakt.ai · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →