AI · alternatives · 2026
24 alternatives to OAuth for AI Agents
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 () => {…
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 1 we have checked on their own sites, 1 of them free or with a free tier.
- 1
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 →
- 2
AgentKeyfree tier▲400One-stop live data marketplace for your agent
Jul 2026 · agentkey.app · its alternatives →
- 3
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 →
- 4
DCP▲104Give your AI agents encrypted permission and keys
May 2026 · dcpagent.com · its alternatives →
- 5
- 6
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com · its alternatives →
- 7
I've been building computer-use tools for a while, and I quietly launched this about a month ago (122 Stars on GH). I figured it was worth sharing here. Over the last few months, a lot of computer-use agents have come out: Codex, Claude Code, CUA, and others. Most of them seem to work roughly like this: 1. Take a screenshot 2. Have the model predict pixel coordinates 3. Click x,y 4. Take another screenshot 5. Repeat That works, but it's slow, expensive in tokens, and fragile. If the UI shifts a few pixels, things break. And the model still doesn't know what any element actually is. But the…
May 2026 · github.com · its alternatives →
- 8
API Radar▲77We built API Radar to track exposed API keys from OpenAI, Claude, Gemini, and other major providers—in real time—from public GitHub repositories. Why? Leaked AI keys are everywhere. They power bots, cost companies thousands, and even expose user data. But no one had a clean dashboard to see the leaks as they happen — until now. What you’ll find: Full redacted + raw API key leaks Real-time feed of exposed repos Leaderboards by author, repo, and provider Filtering by provider (OpenAI, Claude, Gemini, etc.) Timeline of key exposure trends Built for security researchers, devs, and AI companies…
Jan 2026 · apiradar.live · its alternatives →
- 9
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 →
- 10
- 11
Share API keys with AI agents. Encrypted. No server needed.
Feb 2026 · its alternatives →
- 12
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 →
- 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
api2ai parses OpenAPI Spec to generate an agent that can make API calls. For context, I recently need to explore a handful of API suites and thought LLMs can help expedite this process. After some digging, I found OpenAPI Specs are perfect fit for function calling. Based on a text prompt, api2ai can select the right endpoint and properly parse request params and make api calls. It also handles authentication, currently it supports basic auth, api keys, and bearer token schemes. The tool has helped me explore and see APIs in action without a deep dive into the docs or using postman. It’s open…
2023 · github.com · its alternatives →
- 15
Web-scale and security-hardened API key server for users, services, machine to machine, and AI agents. Token derivation brings fine-grained capability tokens to avoid common API key pitfalls. Apache2 open source for indie deployments, commercial for scalable and HA. - ory/talos
Jun 2026 · github.com · its alternatives →
- 16
Stop giving AI agents your API keys in plaintext > Use Vault
Mar 2026 · tryvault.xyz · its alternatives →
- 17KD
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 →
- 18
- 19
Hey HN - I'm Mason, and I'm excited to share AgentCash - a CLI to help your agent discover and pay for premium APIs and paywalled data. The problem we kept running into was simple: if you want an agent to use premium data or services, the setup flow is awful. You have to find the right provider, sign up manually, subscribe, generate an API key, install tooling, and then teach your agent how to use it. Then do that again for the next provider. We wanted a simpler model: give the agent a universal balance, let it discover available resources, and let it pay per call. So AgentCash gives agents…
Mar 2026 · agentcash.dev · its alternatives →
- 20
Your AI has your code's text, never its map. Fix that.
Jun 2026 · luuuc.github.io · its alternatives →
- 21
Hello, my name is Andrei. My friends and I recently built CentralMind Getaway, an open-source tool that automatically generates AI-agent-optimized APIs from your database connection. It’s designed for those who don’t want to expose direct SQL access to their databases and prefer not to spend time building these APIs manually. What it does: - Auto-generates APIs from your database connection, infer schema & sample data using AI - Filters out PII and sensitive data for compliance (GDPR, SOC 2, etc.) - Optimized for AI-Agent with extra meta information and REST and MCP protocol support -…
2025 · github.com · its alternatives →
- 22
A public git host for AI agents. No account, no token, no key: push to a name and the repository exists.
Sep 2026 · agentgit.co · its alternatives →
- 23
Open-source AI browser agent that runs any model you choose
Jul 2026 · opensidekick.app · its alternatives →
- 24
Okta for AI agents. IAM for digital workers.
Nov 2025 · agentsudo.dev · 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 →