Audit log: a census of 149 listings

Agent activity is reviewable as read-only logs on the web layer, but the vendor's own governance guidance has finance checking consumption from screenshots, which implies no exportable administrative audit trail.

Checked 2026-09-27

A searchable audit log records configuration changes with actor, entity, activity and originating interface including API and MCP, and exports to CSV capped at 10,000 rows.

Checked 2026-10-11

Local daemon and Codex wrapper logs are written and tailable with `abg logs`, but these are operational logs, not an administrative audit trail with actor identity.

Checked 2026-10-10

Audit logging is listed as included in custom agent builds, and the service pages describe action receipts and complete action logs for every tool call rather than an optional extra.

Checked 2026-10-11

A signed audit log ships in the box, chaining hashes so that deletion or alteration of a record can be detected rather than merely logged.

Checked 2026-10-11

Audit logging of every action is presented as an Enterprise capability, alongside end-user audit logs; the Pro and Free cards list no audit log.

Checked 2026-10-11

Every automated action is recorded in the Action Trace with the intent, the procedure, the data read and a confidence score, per conversation and across the operation; audit logs are also listed on every plan.

Checked 2026-09-23

Every agent action call is recorded with status, source client, duration and credits spent, but the documented Audit covers execution rather than administrative changes such as credential rotation or plan edits.

Checked 2026-10-03

Its actions are traceable through git, which tags authored and committed changes with '(aider)', and local chat, LLM and analytics logs can be written to files, but there is no tamper-resistant administrative audit trail.

Checked 2026-09-09

A tenant-wide Audit Trail records system events, ingestion, processing and user-initiated actions with the initiator recorded, and those logs can be exported to third-party systems such as Splunk.

Checked 2026-09-24

Enterprise instances can log model requests and responses into the Cloud project for compliance records; nothing describes an administrative action trail, and consumer plans get no audit log at all.

Checked 2026-09-10

A Profile Activity tab records reveals, exports, verification runs, sign-ins and key creation with cost and actor, and the vendor states no spending path is unlogged across app, API, CLI or MCP.

Checked 2026-09-26

Audit records are named as something specified during an integration's exception planning, so they are scoped work rather than a standing feature a buyer gets.

Checked 2026-10-03

Audit logs exist but sit only in the Enterprise column of the plan comparison, so neither self-serve paid tier nor the mid Scale tier gets administrative logging.

Checked 2026-09-10

Comprehensive Audit Trails is ticked for Enterprise and crossed out for Business in the plan comparison.

Checked 2026-09-02

Runtime events including model calls are emitted through Python logging for you to capture, but this is application telemetry rather than a tamper-evident administrative audit trail.

Checked 2026-09-19

An Activity Log records source on/off changes and subscription events per business, and disabling AI identification in the voice greeting is recorded, but the vendor states it is not a full settings audit trail.

Checked 2026-09-11

Logging is promised as part of the integrations they wire up, which is a property of the delivered system rather than an administrative audit trail the buyer can inspect in a vendor console.

Checked 2026-09-11

Call-level auditing is thorough — every rail trigger and disclosure is logged — but no admin-action audit trail is documented.

Checked 2026-09-11

Audit logs appear only in the Enterprise column; Teams admins get usage and member CSV exports rather than a record of administrative actions.

Checked 2026-09-11

A workspace activity log sits under Settings > Audits and a Manager role may view audit records, but the pricing row for it is empty on Free, since it starts at the Plus plan.

Checked 2026-09-02

Deployment logs, call logs and transcripts are recorded per agent; no administrative audit trail of account actions is documented.

Administrative and API actions land in the Compliance API Activity Feed, which Anthropic must enable for the organization; separately the SDK exports per-user tool and permission events over OpenTelemetry.

Checked 2026-09-02

Audit logs are an Enterprise plan feature, alongside a compliance API; cloud sessions log every operation, and OpenTelemetry export works on any plan.

Checked 2026-09-02

Enterprise records authentication events and administrative operations selectively, and member activity logs survive offboarding; full conversation history is captured only if you enable prompt storage to your own bucket.

Checked 2026-09-12

A searchable, exportable administrative audit log covering seats, roles, API keys and config exists, but only for Enterprise organisations and only for admin-level roles.

Checked 2026-09-15

Compliance API audit logs are listed as Enterprise-only; Plus, Pro, Business and API-key use are marked unavailable.

Checked 2026-09-02

The privacy policy says automation records are kept for audit purposes, which is a retention statement rather than a documented administrative audit trail feature.

Checked 2026-09-05

Access logging and real-time activity tracking are listed platform features, and the homepage describes every tenant as audit-logged; retention windows are configurable.

Checked 2026-09-12

The security addendum commits to logging all user actions with timestamps, IP addresses and usernames, and agent releases carry version history and audit trails, but Cresta does not say customers can read or export those logs themselves.

Checked 2026-09-13

The vendor claims audit trails inside the governance layer and revoked role grants are retained for audit, but audit logging is not a listed row on either plan and governance is Enterprise-gated.

Checked 2026-09-13

Enterprise only: JSON audit logs in the dashboard, filterable, with optional streaming to SIEM or S3 on request.

Checked 2026-09-02

Tamper-protected audit logs exist and capture logins and unusual activity, but Decagon states access is limited to its own senior engineering leadership rather than the customer's admins.

Checked 2026-09-14

Per-request logs (90 days in console, longer via the Usage API, with per-request USD cost) plus per-session message observability; no administrative-action audit trail is documented.

Logins are recorded in an enterprise audit log; the docs describe audit logs only at the enterprise level.

Checked 2026-09-02

An organization audit-log endpoint exists in the v3 API but requires an enterprise-level service user with ManageEnterpriseSettings, and queries are capped at 100-day windows.

Checked 2026-09-03

Cloud gives per-app conversation and run logs; tamper-evident audit logs with SIEM streaming are an Enterprise capability.

Checked 2026-09-02

A tamper-evident log distinguishing human from agent actions exists with CSV export and SIEM streaming, but the docs restrict it to the Enterprise plan.

Checked 2026-10-01

OCSF-schema logs over 100 administrative endpoints, pullable into a SIEM, but gated on Enterprise tier plus an API key holding audit_log_read.

Checked 2026-09-02

Enterprise lists user analytics and Scale admins can view team usage, but no log of administrative actions is documented anywhere; the auditability Elicit advertises is of review decisions, not of admins.

Checked 2026-09-14

Every API request is written to an audit log with account, key fingerprint, IP, device and action, though bodies are excluded and retention is not yet fixed.

Checked 2026-10-09

Spend is fully recorded in a credit ledger covering purchases, grants, spends and refunds, but there is no documented log of administrative actions such as key creation or member changes.

Checked 2026-10-03

Business lists audit logging; the organization audit log view and its API are restricted to Enterprise owners.

Checked 2026-09-02

Administrative action is recorded and readable over the REST API — logins, permission and role changes, SCIM provisioning, security settings and data exports — though these are workspace admin events rather than a log of Fin's own answers.

Checked 2026-09-18

Every account gets 24-hour activity logs of API requests, but a durable per-fetch audit trail streamed to your SIEM is Enterprise-gated per organization.

Checked 2026-09-24

Authentication audit logs and log streams are named as Enterprise features, and provider toggles plus connector connections record who changed what, but the docs still list advanced audit logging as not yet shipped.

Checked 2026-09-14

Cloud Audit Logs under serviceName cloudaicompanion.googleapis.com, split into Admin Activity and Data Access entries; code completion and generation calls are themselves audited.

Checked 2026-09-02

Team admins see only per-seat credit usage and seat changes; exportable usage logs and login history for security investigation are unlocked on Enterprise.

Checked 2026-09-15

Enterprise audit logs record plan, policy and licence changes plus agent activity on the website; the Pro+ card also lists audit logs, and Free and Pro get none.

Checked 2026-09-02

Admin audit logs cover configuration and administrative actions with CSV export; default retention is 30 days and end-user activity sits in separate event logs.

Checked 2026-09-02

Execution is recorded in depth through built-in logging, metrics and traces, but this is telemetry about agent runs on infrastructure you own, not an administrative audit trail of who changed what.

Checked 2026-09-15

Every tool invocation, command and timestamp is recorded, but only to local files and a local SQLite session database that are purged after two weeks, so there is no central or tamper-evident administrative trail.

Checked 2026-09-16

Audit logs are marked absent on Pro and present on Enterprise, so administrative traceability requires the sales-led plan.

Checked 2026-09-30

A local audit log of approvals and changes ships free, while searchable cloud decision history is reserved for paid tiers.

Checked 2026-09-29

A full audit trail on every interaction is promised for the private deployment; for the hosted plans only trigger activity counts over 1, 7 or 14 days are documented.

Checked 2026-09-24

The account holder's dashboard records every form prepared or submitted and every email sent with status and replies, but no administrative audit trail or log export is documented.

Checked 2026-09-14

Activity is logged in detail on your own disk — a structured server log plus one file per conversation — but these are operational logs the user can disable or redirect, swept by age after two weeks, not a tamper-evident administrative audit trail.

Checked 2026-09-17

Customer-visible audit logging is named as an Enterprise-only security layer; lower tiers get a usage dashboard instead, and the vendor separately claims internal audit logging of all data queries.

Checked 2026-09-17

Administrative logging exists but is gated: the comparison table crosses it out for the free and both individual paid tiers and ticks it only in the enterprise column.

Checked 2026-09-18

Requests made through the ChatGPT connector are logged so usage can be audited, and connection logs are retained twelve months, but no general administrative audit trail of dashboard or configuration changes is described.

Checked 2026-09-26

Audit logs are an Enterprise feature, absent from Free and Teams.

Checked 2026-09-02

A tamper-resistant log of administrative actions with a UI, an API and 400-day retention exists, but the vendor states plainly it is Enterprise-only: Developer and Plus get nothing.

Checked 2026-09-18

Langflow records API-key usage counts and last-used timestamps in its database and can export traces to an OTLP backend, but no administrative audit trail of who changed what is documented.

Checked 2026-09-25

Administrative action is recorded, but only on Enterprise: a tamper-resistant log of settings, membership, credential and workspace changes, retained up to 400 days and queryable by API.

Checked 2026-09-02

Runs replay step by step and memory revisions are immutable, and the vendor confirms server-side records of API and MCP activity, but no admin-facing audit log or export is documented.

Checked 2026-09-18

The vendor states audit trails are built into the platform alongside access controls, and configuration changes are separately tracked with reviewable, revertable version history.

Checked 2026-09-09

Lindy says every action it takes is logged and visible, but audit logs as an administrative feature are named only in the Enterprise column of the plan table and the Enterprise-only list in the docs.

Checked 2026-09-19

Config changes and observability access are logged internally, but there is no customer-facing audit log export; SIEM export is roadmap only and handled by the account team.

Checked 2026-09-02

Every request carries a correlation ID linking API call, database queries, connector dispatches and model calls into one traceable chain, and access logs are offered for audit review.

Checked 2026-09-09

Audit logs are listed as a Team plan feature alongside the compliance claims; nothing on the pages read says individual and Pro accounts get them, or what events are recorded.

Checked 2026-09-19

Audit logs are named only in the Enterprise tier's bundle; Starter and Teams cards do not list them.

Checked 2026-09-02

Agent decisions and actions are logged, traceable and exportable with SIEM integration, and the vendor separately lists comprehensive audit logging among its platform security controls.

Checked 2026-09-25

Agent actions are traceable via OpenTelemetry, and the FIDES security provider keeps per-session audit records of policy decisions, but there is no administrative action log because there is no admin plane.

Checked 2026-09-19

Audit logs are named as a Business-plan security feature; the lower tiers get API logs and activity history rather than administrative audit records.

Checked 2026-09-20

Settings carries an operation log of security-relevant member actions with time, actor, IP address and login device, although filtering reaches back only three months.

Checked 2026-10-03

A JSON SIEM export over SFTP records authentication, permission changes, config changes and Agent Studio actions, refreshed every three hours.

Checked 2026-09-20

Every run is an append-only event log covering model calls, tool calls and approval decisions, exportable as JSON — but it is a local session record, not a tenant-wide log of administrative action.

Checked 2026-09-20

Audit events and log streaming to a SIEM are Enterprise: the pricing comparison table shows a cross against audit logging and log streaming for Starter and Pro.

Checked 2026-09-02

The user gets a full activity record — every application with filled fields, answers, timestamp and proof screenshot — but there is no organisational admin audit trail.

Checked 2026-09-29

Every agent run is logged locally with steps, clicks and screenshots, but this is an on-device run log, not an administrative audit trail for an organisation.

Checked 2026-10-08

Every automated decision is logged with its reasoning and confidence as a standard layer of the agent architecture they build.

Checked 2026-09-26

Configuration changes are recorded as immutable agent versions with diffs and named automatic backups, but they are purged after about ninety days and there is no account-wide log of administrative or sign-in activity.

Checked 2026-09-09

Built-in tracing records a detailed run history of model calls, tool calls, handoffs and guardrails, but that is execution telemetry rather than a log of administrative actions, and it can be disabled outright.

Checked 2026-09-20

Organisation audit logs are retrievable through the Admin API and its Audit logs endpoint.

Checked 2026-09-02

There is a bounded audit ledger of runs, tool actions and approval decisions, but it is metadata only and the richer execution-identity recording is off by default and must be enabled.

Checked 2026-09-21

Full per-action audit logging is claimed for the Enterprise control plane; the free and Individual tiers carry no such published logging.

Checked 2026-09-21

Audit logs are named on the Enterprise Max card and in the custom governance tier; the comparison table marks the audit-log row 'Contract required'.

Checked 2026-09-02

What is recorded is end-user activity: conversations, action runs and spend per user, which the vendor calls an audit trail. No immutable log of administrative actions is documented.

Checked 2026-09-09

Each run returns its result with sources and completion evidence for review, which is per-run traceability; no account-level log of administrative actions is described.

Checked 2026-10-03

Permission-change audit logging is stated for Enterprise accounts only; every published version and change is separately kept as project history.

Checked 2026-09-02

Approvals and model calls are written to records that cannot be edited or deleted through the platform during retention, including by client or Precision administrators, and each model call records job, model and cost.

Checked 2026-10-06

There is no vendor-side administrative log, but every model call and tool call is emitted as standard OpenTelemetry spans you can send to Logfire or any OTLP backend you already run.

Checked 2026-09-21

Auditability is claimed as a property of the Enterprise SAML SSO feature; no separate admin audit log is documented.

Checked 2026-09-02

Audit logging exists but only on Enterprise, where events and execution traces are streamed out over OpenTelemetry; Pro and Team are marked as not having it.

Checked 2026-09-22

Audit logging, SIEM streaming and the prompt-retrieval compliance API exist, but only on Enterprise and only for account admins.

Checked 2026-09-22

Agent configuration changes are recorded as immutable published versions with browsable history and side-by-side comparison; no workspace-level log of administrative actions such as role changes or key rotation is documented.

Checked 2026-09-02

Review actions and block list additions taken through the API are recorded in an account audit log against the token label; no broader admin audit trail is documented.

Checked 2026-10-11

Every CRM write-back is logged who/what/when/result and all plans get an agent activity log with an admin roll-up, but the 'Audit Logs' row is ticked only under Enterprise.

Checked 2026-09-03

Audit logging appears once, bundled with RBAC in the enterprise-tier feature list, and no entry or mid package mentions any record of administrative action.

Checked 2026-09-28

Agent actions and outputs are recorded for governance, and Observability adds per-turn session traces; event-level logging with SIEM streaming and Field Audit Trail are the paid Salesforce Shield add-on.

Checked 2026-09-03

Every MCP tool call is logged with payload and timing detail and kept for ninety days, on both the monthly and annual plan.

Checked 2026-09-25

A permanent ledger records every agent action with before and after state, surfaced as an activity feed; it covers agent edits rather than billing or admin events specifically.

Checked 2026-10-03

Agent decisions, tool calls and suppressions are auditable in Insights and Horizon; logging of administrative actions by staff is not documented publicly.

Checked 2026-09-26

Tamper-evident organization audit log with UI, API and CLI access, documented under the Enterprise section.

Checked 2026-09-03

Agent runs, credit charges and each chat step are logged and readable in-app, but no admin-action audit log or log export is documented; CRM changes rely on the CRM's own trail.

Checked 2026-09-15

Run-level activity and project version history are recorded and downloadable, but no page documents an audit trail of administrative actions such as role or policy changes.

Checked 2026-09-09

API logs give an audit trail of every request an agent makes, with retention set by plan; no admin-action audit log is documented.

Checked 2026-09-03

An audit trail records actions and approval decisions with their actor and time, and the vendor documents audit-log integrity for tamper evidence.

Checked 2026-10-03

Run-level records are part of delivery — structured logs, alerting and a dashboard of call transcripts and audio — but no administrative audit trail of who changed what is described.

Checked 2026-09-12

Audit trails are documented for TelEcho staff access to customer data, and calls carry session replay and transcripts, but no customer-visible log of administrative or configuration changes is described.

Checked 2026-09-16

An audit events API returns who changed what and when, including whether the change came from Telnyx, the owner, an organization member or an account manager, though the vendor calls it best-effort.

Checked 2026-09-09

Audit logs are listed as an Enterprise addition; pay-as-you-go accounts get run logs, screenshots and source URLs instead.

Checked 2026-09-03

Every agent inherits platform audit logging, but the searchable and exportable audit row is an em dash on Basic and starts at Standard, and the docs limit audit export itself to the Enterprise licensing plan.

Checked 2026-09-03

Admins receive usage reports on member accounts, but no audit log of administrative action appears in the Enterprise feature list or the security overview.

The DPA commits to event logging of production infrastructure for security purposes; no customer-facing admin audit log is documented.

The dashboard keeps org-wide API, call and webhook logs and assistant version history; no member-action audit trail is documented.

Checked 2026-09-03

Agent tool calls are logged and every scheduled run leaves a record; no administrative audit log of member, permission or billing changes is documented.

Checked 2026-09-03

Per-action attribution exists for teammates and is retained for the life of the owner's account, but the vendor documents no exportable administrative audit trail for settings or billing changes.

Checked 2026-09-22

Immutable audit trails for administrative action are asserted as EqualyzAI's own security control; no customer-visible audit log appears in any plan or in the docs, where Growth's export is call logs in CSV/JSON.

Checked 2026-09-03

Login and audit events are recorded and security logs kept for about twelve months, but these are vendor-side security logs; no customer-visible administrative audit trail or export is described on any tier.

Checked 2026-10-03

Audit logging is listed platform-side, and each API tool call can carry a stored reasoning note.

Checked 2026-09-03

Warp logs agent actions, and an Enterprise analytics API returns message-level events for compliance review, but it needs an admin toggle and there is no audit trail of admin configuration changes.

Checked 2026-09-03

The API exposes a per-session work log and account spending history, which records what the agent and your credits did, but nothing described covers administrative actions by an organisation's users.

Checked 2026-09-27

Each session writes a local event log and raw tool output to disk, which is a developer record rather than an administrative audit trail.

Checked 2026-09-21

Authentication, user-management, configuration and usage events are recorded and exportable as CSV, but only from Pro Plus upward — the entry Pro tier has none.

Checked 2026-09-09

Account audit logs are Enterprise-only: the comparison table shows an em dash for Support Team, Suite Team and Suite Professional.

Checked 2026-09-03

Every session is written locally as a JSONL transcript with tool calls and results, but the vendor explicitly disclaims the extension event stream as an audit log and there is no central record.

Checked 2026-09-28

Audit logging is standard in what they build, named both in the AI security approach and as an enterprise deliverable alongside encryption and role-based access control.

Checked 2026-09-25