Audit log
Recorded call metadata, execution filters, live tail, and programmatic audit access.
Every call Arc0 mediates — allowed, blocked, or failed upstream — is written to the audit log. That's true on every plan, including free.

What's on an event
Each row is one call, with fields including the agent (agentId), the connected user
(connectedUserId, externalUserId), the customer, the connection used, the app and action, the
scope, and how the call arrived (via: mcp, sdk, rest or proxy, shown as "Arc0 MCP",
"SDK", "REST API" or "Authenticated proxy"). It also carries which policy and rule decided it, the
reason, the upstream status if the call reached the app, and latency.
The current console details drawer shows redacted execution metadata. It does not expose request or response bodies, credentials, or tokens.
Decisions
A call's decision is one of allowed, blocked or error — "approval" isn't a fourth stored
value. It's what the UI calls a blocked call that has an approval attached, filtered and labeled
Needs approval. The four labels you'll see are Allowed, Blocked, Needs approval and Error,
with its HTTP status appended.
Filters and URL params
Every filter is a URL param, so a filtered view is a link you can save or send:
| Param | Values |
|---|---|
q | Free text — action, user id or reason |
range | 1h, 24h (default), 7d |
decision | allowed, blocked, approval, error |
scope | read, write, destructive |
app, agent | App id, agent id |
user, policy | URL-only, not exposed as filter controls |

A Live indicator shows the log is streaming, with an Export button next to it for pulling the current filter to a file.
Call details and redaction
The console execution drawer shows the call ID, app, exact action and version, execution status, project, start/finish times, duration, access source, provenance and error code. Embedded project logs also show the end-user identity. Unfinished calls have no final duration.
Request arguments, provider response bodies, credentials and tokens are excluded. Opening a call does not decrypt retained execution payloads. Caller-bound runtime execution receipts are a separate API contract; see Programmatic access.
Retention
Audit events are kept for 7 days on Personal, 30 on Build, 90 on Launch, and 365 on Scale, with custom retention on request. The audit page states its own plan's window directly: "Kept 90 days on Launch."
Console execution logs
The console execution log supports a 7-, 30-, or 90-day range and filters for app, end user, status, and exact action. Each call shows its duration after completion; running calls have no final duration. Turn on Live tail to poll for recent calls using the current filters. Open a call to inspect its redacted metadata in the details drawer. Direct workspaces show only your own calls and do not offer an end-user selector.
The screenshot examples above illustrate the fixture dashboard. The implemented console and management execution logs return redacted metadata.
Programmatic access
GET /v1/audit lists audit events in the calling business key's bound project. It requires
audit:read and accepts event, actorId and resourceId filters, plus limit (1–100,
default 50) and cursor. The response is {data, nextCursor}; each row includes id,
actor_id, event, resource_id, metadata and created_at. Cursors cannot be reused
for a different project or filter set. User-bound runtime keys cannot call this endpoint.
GET /v1/execution-logs provides filtered, paginated execution metadata with audit:read.
It accepts range (7d, 30d, or 90d), app, endUserId, status, and exact action,
plus limit and cursor. Completed rows include duration_ms; unfinished rows use null.
There is no public audit-detail endpoint or SDK audit helper. Audit rows do not disclose
provider credentials or full retained provider request/response bodies. For an individual
runtime call, use GET /v1/executions/:executionId (with endUserId for a business key),
getExecution(id) in TypeScript or get_execution(id) in Python. These return caller-bound
execution receipts. See the API reference and its generated OpenAPI
for the management and runtime contracts.

