Gazebo
    ServicesAgentsDocsSpecWritingPricing
    Log inSign up
    Log in

    Overview

    • Introduction
    • Changelog
    • Implementations

    Identity

    • Identity declaration
    • Scope syntax

    Consent

    • The consent token
    • Verification

    Runtime

    • Overview
    • Access policy
    • Audit log
    • Credential broker
    • Compliance mappings

    Implementing AIP

    • Compatibility guide
    AIP Specification

    Overview

    • Introduction
    • Changelog
    • Implementations

    Identity

    • Identity declaration
    • Scope syntax

    Consent

    • The consent token
    • Verification

    Runtime

    • Overview
    • Access policy
    • Audit log
    • Credential broker
    • Compliance mappings

    Implementing AIP

    • Compatibility guide
    SpecRuntimeAudit log

    Audit Log

    A conforming implementation must produce an audit log entry for every credential retrieval and every approval decision, including approved, denied, and pending-approval outcomes. The audit log is the primary mechanism for accountability and compliance verification.

    Minimum fields

    {
      "$schema": "https://schema.gazebohq.com/v0.1/audit-log.json",
      "log_version": "1.0",
      "event_id": "evt_01j9xkq3m4...",
      "timestamp": "2026-08-10T09:14:02Z",
      "agent_id": "stripe-payment-monitor",
      "install_id": "...",
      "service": "stripe",
      "operation": "POST /v1/charges",
      "authorization_basis": "policy:stripe:charges:create",
      "outcome": "approved",
      "approval_required": false
    }
    

    Fields

    FieldRequiredDescription
    $schemayesMust be https://schema.gazebohq.com/v0.1/audit-log.json. Required in every conforming entry.
    log_versionyesAudit log schema version. Must be "1.0" for AIP v0.1.
    event_idyesIdentifier unique within the issuing provider. Immutable after write.
    timestampyesISO 8601 UTC timestamp of the event.
    agent_idyesThe agent that made the request.
    install_idyesThe specific installation — links the event to a consent token and user.
    serviceyesThe service the agent attempted to access.
    operationyesThe operation attempted (e.g. HTTP method + path, or named action).
    authorization_basisyesStable provider-defined identifier for the policy rule that authorised or denied the operation.
    outcomeyesOne of approved, denied, or pending_approval.
    approval_requiredyesWhether the operation triggered an approval rule.

    Immutability

    Audit log entries must not be modified after write. Implementations must use append-only storage or an equivalent write-once mechanism. Log entries are evidence — retroactive modification voids their compliance value.

    Retention

    Implementations should retain audit logs for a minimum of 90 days. Compliance-oriented deployments (SOC 2, HIPAA) typically require 12 months. Retention policy is implementation-defined; the spec defines the minimum fields, not the storage mechanism.

    Access policyCredential broker
    Gazebo

    IAM for AI agents. Scoped credentials, access policies, and audit trails — without rotating keys.

    Product

    • Pricing
    • Status

    Explore

    • Services
    • Agents
    • Workflows
    • Integrations

    Content

    • Writing
    • Topics
    • Blog
    • Docs

    Free Tools

    • Scanner

    Company

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

    © 2026 Gazebo. All rights reserved.

    PrivacyTermsSecurity