Every agent run records a canonical execution trace: an ordered stream of events describing everything the run did — which tools it called and what they returned, reasoning summaries, progress updates, browser sessions, and changes to its output artifacts. This is the same event stream that powers the live Activity view in the Agent playground.
What it's for#
- Debugging runs — see the exact searches, scrapes, and extractions the agent performed, each tool's input (
tool_call.started) and result (tool_call.finished), and where a run went wrong (error.occurred, and the terminalrun.finishedevent'soutcomeand structurederror). - Live progress UIs — poll the trace while a job is
processingto show what the agent is doing in real time.progress.reportedevents carry the run's phase (planning,working,finalizing) with a human-readable message, andreasoning.summaryevents narrate the agent's thinking. - Live browser view — pass
?liveView=truewhile a run is in flight to getactiveBrowserSessions: the run's active browser sessions, each with aliveViewUrlyou can embed to watch (or demo) the agent browsing. - Cost tracking —
creditsUsedreports credits consumed so far, capped at the run'smaxCreditsif one was set.
How it works#
Events are emitted by the run's agents — the orchestrator and its subagents — and each event identifies its emitter in the agent field. Browser work happens inside an agent's own browser session and is reported through browser.session.* events, not by separate browser agents. Order events by producerSequence (per emitting agent). The type field discriminates the 13 event variants; see the response schema below for the full list and each variant's fields.
artifact.updated events don't carry the artifact content itself — they reference it by snapshotId, which you fetch with the snapshot endpoint.
Events can continue to land for a moment after run.finished arrives, so if you're polling a live run, keep a short tail window open before rendering the final state.
400.Are you an AI agent that needs a Firecrawl API key? See firecrawl.dev/agent-onboarding/SKILL.md for automated onboarding instructions.

