Gazebo
    ServicesAgentsVaultsDocsWritingPricing
    Log inSign up
    Log in

    IAM for AI agents

    Secure credential management for every AI agent.

    Connect services such as Stripe, GitHub, Cloudflare, and Vercel once, then control which credentials each agent can retrieve. Review credential-access logs and revoke future retrieval per agent.

    Get started free How it works

    No credit card required.

    Encrypted at rest with AES-256-GCM. Authorized retrieval returns the provider key to the agent runtime.

    Try the interactive demo

    No signup. No real API keys.

    Connect services

    StripeCloudflareVercelResendGoogle+ any API

    Credential Activity

    Last 24 hours
    09:14:02cursor-agentStripeCredential request · POSTapproved
    09:11:47cursor-agentCloudflareCredential request · POSTapproved
    09:08:30claude-agentVercelCredential request · POSTdenied
    08:55:12cursor-agentStripeCredential request · GETapproved

    Access Profile

    cursor-agent

    Active
    Stripe On
    Cloudflare On
    Vercel Off
    Resend Off

    Access Denied

    Blocked
    Agentclaude-agent
    ServiceVercel
    ReasonNot in access profile

    Request blocked automatically. No key exposed.

    You have IAM for your team. Not for your agents.

    Hardcoded and shared API keys give agents more access than they need. Gazebo gives each agent its own scoped identity, records every credential request, and lets you revoke one agent without disrupting the others.

    Without Gazebo

    Agents inherit full access from shared API keys.
    Every new agent gets the same permissions.
    No read/write controls — agents can do anything the key allows.
    If something goes wrong, you're left piecing together logs.
    Revoking one agent often means rotating credentials for everyone.

    With Gazebo

    Every agent gets its own scoped identity.
    Each agent can retrieve only the service credentials you allow.
    Credential-release policies per agent — choose permitted services and declared retrieval methods.
    Credential-access logs record retrieval, not later provider actions.
    Revoke future retrieval per agent; leaked provider keys may still need rotation.

    How it works

    Connect once. Give each agent only the access it needs.

    Gazebo stores your service credentials, gives each agent a scoped access profile, and enforces that profile every time the agent requests access.

    1

    Connect your services

    Store service credentials centrally instead of distributing keys through configuration files. Authorized retrieval still delivers the actual key to the agent runtime.

    StripeConnected
    GitHubConnected
    CloudflareConnected
    2

    Define the agent's access

    Create an access profile for your agent. Choose its service credentials and permitted declared methods. Use provider scopes to restrict the actions a retrieved key can perform.

    cursor-agent
    StripeGET + POST retrieval
    CloudflareGET retrieval
    VercelNo retrieval
    3

    Enforce and audit requests

    Gazebo checks the agent's policy, allows or blocks the request, and records the result in the audit log.

    cursor-agent → StripeAllowed
    GET /v1/webhooks
    cursor-agent → VercelBlocked
    POST /v9/env

    Contain the blast radius.

    Each agent gets a scoped Gazebo token and can retrieve only the credentials you approve. Use provider-restricted keys to limit what those credentials can do.

    Revoke future retrieval. Without rotating your keys.

    Invalidate one agent's Gazebo token immediately without disrupting other agents. Keys already retrieved remain usable until they expire or are restricted or revoked at the provider.

    Know exactly what happened — and who did it.

    See which agent requested access, which service and operation it requested, and whether Gazebo allowed or blocked it.

    MCP native

    Connect the agents you're already using.

    Use OAuth in supported clients to approve only the service keys each connection needs. Compatible remote HTTP clients can also use a scoped agent token. Gazebo checks the connection's credential-retrieval policy on every request.

    MCP endpoint

    https://app.gazebohq.com/api/mcp

    Connect with OAuth, or use a scoped agent token.

    Building your own tools? Use the Direct agent API.

    Tested with

    Cursor Desktop

    Connect with OAuth and approve selected service keys

    Claude Chat & Desktop

    Connect with OAuth and approve selected service keys

    ChatGPT Business — web

    Connect with OAuth and approve selected service keys

    Claude Code — desktop

    Tested in the desktop Code session through OAuth

    Devin hosted

    Connect your hosted agent with Personal OAuth

    Codex CLI

    Native MCP tool calls tested with a scoped agent token

    OpenAI Responses API

    Use Gazebo tools from your model-driven workflow

    Test coverage varies by client and runtime. See the compatibility guide for details.

    Client setup and compatibility →

    Building agents for other users?

    Add a hosted consent screen for signed, scoped authorization.

    Explore Agent Consent Flow

    Frequently asked questions

    What is IAM for AI agents?

    Gazebo gives each agent a separate identity, controls which service credentials it may retrieve, and records credential access. The agent still receives the configured provider key; use provider scopes or IAM to restrict what that key can do.

    How is Gazebo different from a secrets manager?

    A secrets manager (like HashiCorp Vault, AWS Secrets Manager, or 1Password) stores your credentials securely. Gazebo sits on top of that: it's the access-control and audit layer that decides which AI agent can retrieve which credential, logs every retrieval, and lets you revoke one agent's access without rotating the underlying key.

    What happens if an AI agent is compromised?

    Revoke the Gazebo agent to block future credential retrieval, then investigate provider activity and any keys already retrieved. A retrieved key retains its provider permissions; if it may have leaked, revoke or rotate it at the provider. Use trusted runtimes and narrowly scoped provider keys.

    Do I need to rotate my API keys to revoke an agent's access?

    Revoking its Gazebo token blocks future retrieval without rotating a provider key. But a key already retrieved remains usable within provider permissions. If the key may have leaked, provider-side revocation or rotation may be necessary and can affect other consumers.

    Does Gazebo work with MCP-based agents like Cursor and Claude Code?

    Gazebo supports remote Streamable HTTP MCP with OAuth or scoped agent tokens. Cursor Desktop, Claude Desktop, Claude Code's desktop connector and Devin's hosted agent have tested OAuth paths. Other clients need compatible transport and authentication; follow the client setup guide. Gazebo limits credential retrieval, while provider key permissions govern subsequent API calls.

    Can I give one agent read-only access while another has full write access?

    Use provider credentials with genuinely different read/write permissions. Gazebo also checks the method an agent declares when requesting a credential, but it does not proxy or restrict the provider calls made after retrieval. A GET release policy cannot turn a write-capable key into a read-only key.

    Learn about AI agent security

    All posts

    AI Agent Credential Management: Provision, Audit, Revoke

    An owner, action and evidence checklist for onboarding agents, reviewing credential access, responding to incidents and offboarding safely.

    July 22, 2026

    Pasting API Keys into AI Agent Prompts: The Risk

    Trace possible prompt disclosure, understand client-specific retention and respond to an exposed key without assuming tool-based retrieval keeps values hidden.

    July 15, 2026

    MCP Security: Authentication, Tool Trust and Credential Access

    Assess MCP authentication, execution hosts, tool trust and credential handling. Separate retrieval policy from provider permissions and downstream evidence.

    July 3, 2026

    Stop sharing API keys between agents.

    Connect your services once, define each agent's access, and audit every credential request.

    Get started free
    Gazebo

    Credential management for AI agents. Control credential retrieval, review access logs, and revoke an agent’s future retrieval without rotating shared API keys.

    Gazebo

    • Account
    • Demo
    • Pricing

    Explore

    • Services
    • Agents
    • Vaults

    Developers

    • Docs
    • SDK
    • CLI
    • API
    • MCP

    Content

    • Writing
    • Topics
    • Blog

    Company

    • About
    • Contact
    • hello@gazebohq.com

    © 2026 Gazebo. All rights reserved.

    PrivacyTermsSecurity