Trace API for agents
Currents has a trace API made for agents. Instead of downloading a Playwright trace, an agent reads it one part at a time and picks each next call from what it just read.

Currents now has a trace API, made for agents. A Playwright trace is a zip of several megabytes with every action, the page after each action, every network request and the screen. Instead of downloading it, an agent asks the trace API for one part at a time: the summary first, then only what the summary points to.
Each answer is small, so the agent spends few tokens and picks its next call from what it just read. Here an agent finds why a checkout freezes:
The trace API returns any part of the trace:
- Steps — each action with its time, the failed action and its error, page errors, console errors and failed requests
- DOM snapshots — the page at any moment, as text, as the accessibility tree, or as HTML that opens in a browser
- Network requests — filter by status, URL or request body, then read the body the page sent and the response
- Frames — the screen at the failure or at any time
- Filmstrip — frames of the run in one image, up to the failure
- Animation — the recording as a GIF or WebP, rendered when you ask for it
- Files — the files the test saved in the trace, such as Playwright's error context


Get a trace API link
Every Playwright trace in Currents, from a CI test or a session, has a trace API link. The link is public: an agent opens it without a Currents login or an API key. Get one from:
- The Fix link of a failed test
- A Shared Run
- The GitHub run comment
- A session
- The Currents MCP server
- The REST API, which creates a link for any test or session trace
Learn more: