AI · alternatives · 2026
24 alternatives to Fullmakt
Scoped, revocable credentials for AI agents — fully audited
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
- 2
Many teams connecting LLMs to external tools eventually encounter the same architectural issue: as more tools and agents are added, the integration pattern becomes an N×M mesh of direct connections. Each agent implements its own auth, retries, rate limiting, and logging; each tool needs credentials distributed to multiple places and observability becomes fragmented. We built LLM gateway with this goal to provide a single place to manage authentication, authorization, routing, and observability for MCP servers, with a path toward a more general agent-gateway architecture in the future. The…
Dec 2025 · truefoundry.com · its alternatives →
- 3
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 →
- 4
Give AI agents access to real-time data across 200+ apps
May 2026 · apideck.com · its alternatives →
- 5
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 →
- 6
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 →
- 7
- 8
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 →
- 9
Hi HN! We’re the team behind Fiddler, and we recently built an Agent Cache feature. It works by capturing an LLM request/response pair and, once caching is enabled, serving subsequent matching calls locally so duplicate requests never hit the provider. It’s meant to reduce three pains that show up together in agent development: token cost, feedback-loop latency, and output non-determinism. We’d love to hear your thoughts.
Aug 2026 · telerik.com · its alternatives →
- 10
Hi HN, Gabriel, Co-Founder at Permit.io. We're releasing Permit MCP Gateway today, an authorization proxy for MCP servers. TL;DR - we built an MCP Gateway that developers love and CISOs trust. Watch more[0] Now, after your little hate on using fancy copy on HN, to the real thing: MCP is in a strange place. Developers are debating whether it's overcomplicated compared to CLIs or skills files. Meanwhile, enterprises are adopting it by default because every agentic system that acts on your behalf, Cursor, Claude, Copilot, internal agents, needs a stable infrastructure for connecting to tools.…
Mar 2026 · permit.io · its alternatives →
- 11
Clawcard▲125While building Latch, our governance and observability platform for agents handling sensitive operations, I needed a way to test it end‑to‑end. That meant giving agents real, governed identities: email, phone, payments, and secrets - all tied to a single auditable entity. That testing surface turned into Clawcard. With a single API key, your agent gets: - A real email inbox (send + receive) - An SMS phone number - Virtual Mastercards with spend limits - An encrypted credential vault - A full audit trail for every action All of it is built for agent-native governance and wired to work out of…
Mar 2026 · clawcard.sh · its alternatives →
- 12
Mailgent▲51Give your AI agent a real inbox, vault, calendar, and verifiable identity — plus a USDC wallet to pay for what it uses. One API.
Jun 2026 · mailgent.dev · its alternatives →
- 13
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 →
- 14
- 15
Local-first MCP mini-vault: let AIs call external APIs without ever seeing your keys. - RachidChabane/mcp-secrets-vault
2025 · github.com · its alternatives →
- 16
Grantex▲1OAuth 2.0 for AI agents — scoped, revocable, auditable
Mar 2026 · grantex.dev · its alternatives →
- 17
AxioRank▲9The security gateway for AI agents | identity, policy, audit
Jun 2026 · axiorank.com · its alternatives →
- 18
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 →
- 19
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 →
- 20
As a Security Engineer with over 10+ years in industry, I kept running into the same problem with coding agents: Instructions are not guarantees. I put guidance in `CLAUDE.md`, `AGENTS.md`, memory files, MCP descriptions, and tool documentation. I explicitly told the agent things like: - Use the code graph for architecture questions instead of grepping the repository. - Do not use deprecated APIs or Unsafe code. - Prefer specific tools for specific tasks. The agent would still ignore those instructions surprisingly often. It would grep the entire repo, use deprecated APIs, or choose a slower…
Apr 2026 · sigmashake.com · its alternatives →
- 21
- 22
cMCP: Confidential MCP Gateway. Hardware-attested policy enforcement for MCP tool calls. - agentrust-io/cmcp
Aug 2026 · github.com · its alternatives →
- 23
- 24KD
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 →
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 →