Cred
OAuth credential delegation for AI agents
Cred launched on April 9, 2026 with 97 votes, #430 of 21,248 launches that month and more than 95% of that year's launches.
What it does
AI agents need OAuth tokens for user accounts, but most frameworks store them in plaintext config files. Cred is open-source credential delegation middleware. The user consents once. Cred encrypts the refresh token (AES-256-GCM) and never returns it. Agents get short-lived tokens on demand. Every delegation produces a cryptographic audit receipt. We also ship CredX: a single-command encrypted credential store for agents who don't need the full SDK. Self-hosted. Apache 2.0. Zero cloud dependency.
Cred is credential delegation middleware for AI agents. When your agent needs to access a user's Google Calendar, Slack workspace, or GitHub repos, Cred validates the agent's identity, checks that the user consented, and returns a short-lived access token. Refresh tokens never leave the vault.
Open-source, self-hosted credential delegation for AI agents. Cred brokers OAuth tokens so agents get short-lived credentials while refresh tokens stay locked in the vault. Deploy the self-hosted broker, configure your OAuth providers (Google, GitHub, Slack, etc.), and hand your agent a bearer token plus server URL. Cred handles the authorization flow, PKCE, and token exchange. The user connects their Google/GitHub/Slack account through a standard OAuth flow. They choose exactly which scopes to grant to your app. Revocable anytime. Your agent calls cred.delegate() and receives a short-lived access token. The refresh token never leaves the vault. Cryptographic receipts log every delegation.…from cred.ninja
Does a similar job
all alternatives →
Agent Vault – Open-source credential proxy and vault for agentsApr 2026 · github.com · ▲156Hey 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…
- KDKontext.dev – Runtime Credentials for AgentsMar 2026 · kontext.dev · ▲6
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…
Kontext CLI – Credential broker for AI coding agents in GoApr 2026 · github.com · ▲70We 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…
keychains.devFeb 2026 · 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…
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 ↗
Launched alongside, April 2026
the whole month →
- AG
Thought the resources for GPU arch were lacking, so here we are
Life & fun · Apr 2026 · jaso1024.com
Built a ~9M param LLM from scratch to understand how they actually work. Vanilla transformer, 60K synthetic conversations, ~130 lines of PyTorch. Trains in 5 min on a free Colab T4. The fish thinks the meaning of life is food. Fork it and swap the personality for your own character.
AI · Apr 2026 · github.com
I made a laptop stand out of solid concrete, in the style of brutalist architecture, with themes of urbex and urban decay
Life & fun · Apr 2026 · sam-burns.com
With social media and now AI, its important to keep the indie web alive. There are many people who write frequently. Blogosphere tries to highlight them by fetching the recent posts from personal blogs across many categories. There are two versions: Minimal (HN-inspired, fast, static): https://text.blogosphere.app/ Non-minimal: https://blogosphere.app/ If you don't find your blog (or your favorite ones), please add them. I will review and approve it.
AI · Apr 2026 · text.blogosphere.app