AgentGate
An API gateway that lets AI agents call GitHub, Slack, or Google Workspace on a user's behalf without ever seeing the real credentials.
🔗 Visit AgentGate
Description
Giving an AI agent access to your GitHub or Slack account usually means handing it an API token directly, which means if the agent misbehaves or gets compromised, so does your account. AgentGate sits in between: the agent asks it to perform an action, AgentGate does the actual authenticated call, and the agent never touches the real token.
AgentGate is an API gateway acting as an intermediary between AI agents and SaaS platforms like GitHub, Slack, and Google Workspace. It handles OAuth flows, encrypts stored credentials (AES-256-GCM), proxies the actual requests, and keeps a gap-free, cryptographically signed audit log (Ed25519) of every action taken, verifiable offline without needing access to the gateway itself. It ships as a self-hosted Go service with per-agent-per-service rate limiting and a Go SDK for programmatic integration.
💬 Our review
The short version: AgentGate addresses a real and growing risk, AI agents holding raw API credentials, with a sound architecture (token vault plus signed audit trail), but it's a brand-new open-source project with no adoption history yet.
There's no widely established direct competitor doing exactly this token-brokering-for-agents pattern yet, most teams today just hand agents raw tokens and hope for the best, or build ad-hoc credential scoping themselves. AgentGate's cryptographic, offline-verifiable audit receipts are a genuinely useful compliance feature that homegrown solutions rarely bother building. It's free and self-hosted, so the cost of trying it is setup time; worth adopting specifically if you're already worried about agent credential exposure and want an audit trail to show for it.
💰 Pricing
📊 Global score
🤖 AI-enriched data
Gratuit, open-source, auto-hébergé
Pros
les agents IA n'accèdent jamais aux vrais tokens/credentials
coffre-fort de credentials chiffré (AES-256-GCM)
audit trail cryptographiquement signé, vérifiable hors-ligne
gratuit, open-source, auto-hébergé
SDK Go pour intégration programmatique
Cons
projet tout jeune, zéro retour d'adoption
nécessite d'héberger et maintenir soi-même le gateway
couverture limitée aux plateformes déjà intégrées (GitHub, Slack, Google Workspace)