Gazebo
    ServicesAgentsDocsSpecWritingPricing
    Log inSign up
    Log in

    Getting Started

    • Introduction
    • How Gazebo works
    • Core concepts
    • Quickstart

    Agent Access

    • Access profiles
    • Bearer tokens
    • Audit logs

    MCP

    • Overview
    • Cursor
    • Claude Code
    • Windsurf
    • Any MCP client
    • Get credential reference

    Open Standard

    • Agent Consent Flow
    • Agent Identity Protocol (AIP) ↗

    REST API

    • Overview
    • Authentication
    • Services
    • Agents
    • Access policies
    • Audit events
    • Consent administration
    • Agent credential access
    • Errors and limits

    Security

    • Overview
    • Encryption model
    • Credential storage
    • Audit and compliance
    • Responsible disclosure
    Documentation

    Getting Started

    • Introduction
    • How Gazebo works
    • Core concepts
    • Quickstart

    Agent Access

    • Access profiles
    • Bearer tokens
    • Audit logs

    MCP

    • Overview
    • Cursor
    • Claude Code
    • Windsurf
    • Any MCP client
    • Get credential reference

    Open Standard

    • Agent Consent Flow
    • Agent Identity Protocol (AIP) ↗

    REST API

    • Overview
    • Authentication
    • Services
    • Agents
    • Access policies
    • Audit events
    • Consent administration
    • Agent credential access
    • Errors and limits

    Security

    • Overview
    • Encryption model
    • Credential storage
    • Audit and compliance
    • Responsible disclosure
    DocsREST APIAudit events

    Audit events

    The audit log is made up of individual audit events. Each event records an agent credential request and its outcome without including the credential value.

    List credential-access events

    GET /api/v1/audit-events
    

    Requires an account API token.

    curl "https://app.gazebohq.com/api/v1/audit-events?limit=50&service=stripe&outcome=success" \
      -H "Authorization: Bearer YOUR_ACCOUNT_API_TOKEN"
    

    Query parameters

    ParameterDescription
    limitEvents per page, from 1 to 200. Defaults to 50
    cursorOpaque cursor returned by the previous page
    agent_idFilter by one agent ID
    serviceFilter by normalized service identifier
    outcomeFilter by success, denied, or not_found
    fromInclude events at or after this ISO 8601 timestamp
    toInclude events at or before this ISO 8601 timestamp

    Filters can be combined. All results remain scoped to the account that owns the API token.

    Response

    {
      "events": [
        {
          "id": "event-id",
          "agentId": "agent-id",
          "agentName": "Support triage",
          "service": "stripe",
          "keyName": "primary",
          "action": "read",
          "outcome": "success",
          "method": "GET",
          "createdAt": "2026-09-04T05:45:12.000Z"
        }
      ],
      "nextCursor": "eyJjcmVhdGVkQXQiOi...",
      "hasMore": true
    }
    
    FieldDescription
    idStable event identifier
    agentIdAgent that made the request
    agentNameCurrent agent name, or null if unavailable
    serviceRequested service
    keyNameRequested credential name, primary, or all
    actionRecorded operation; currently read
    outcomesuccess, denied, or not_found
    methodIntended HTTP method
    createdAtEvent time as an ISO 8601 timestamp

    Events are account-scoped, ordered newest first, and never contain credential values.

    Pagination

    When hasMore is true, pass nextCursor unchanged as the next request's cursor:

    curl "https://app.gazebohq.com/api/v1/audit-events?limit=50&cursor=NEXT_CURSOR" \
      -H "Authorization: Bearer YOUR_ACCOUNT_API_TOKEN"
    

    Keep the same filters while following cursors. A cursor is opaque and should not be parsed or modified by clients. When hasMore is false, nextCursor is null.

    Plan-specific retention windows are not yet enforced. Retention limits shown on the pricing page are beta limits and will apply when entitlement enforcement is introduced.

    Legacy endpoint

    GET /api/v1/agents/credential-events remains available for existing integrations. It returns a plain array containing up to the 200 newest events, but does not support filters or pagination. New integrations should use /api/v1/audit-events.

    Explore Gazebo

    Gazebo gives each agent an independent access boundary around your agent credentials, with controls for approval, auditing, and revocation.

    Scoped identities for AI agentsGive every agent only the credentials it needs.Credential security and audit controlsSee how access is protected, recorded, and revoked.
    Access policiesConsent administration
    Gazebo

    Credential management for AI agents. Scoped access, approval controls, and complete audit logs—without hardcoding or rotating shared API keys.

    Gazebo

    • Platform
    • Agent Consent Flow
    • Pricing
    • Status

    Explore

    • Services
    • Agents
    • Vaults

    Content

    • Writing
    • Topics
    • Blog
    • Docs
    • Spec

    Free Tools

    • Scanner

    Company

    • About
    • [email protected]
    • [email protected]

    © 2026 Gazebo. All rights reserved.

    PrivacyTermsSecurity