AI Agent Profiler beta

See what your agents repeat and what it costs, without uploading raw traces.

A small client on your computer turns your agent's traces into a reduced copy. You read that copy, you decide whether to send it, and the report keeps what was measured apart from what was estimated.

The original

Stays on your machine. One tool call and its result, abridged.

  • sessionId5eb561a4-2163-6369-8b52-9b4a97b75092becomes a pseudonym
  • cwd/home/dev/billing-serviceproject name becomes a pseudonym
  • gitBranchmaindropped
  • version2.1.0kept
  • commandpython -m pytest -q tests/test_users.pyknown program kept, full input becomes a pseudonym
  • descriptionRun users testspart of the input pseudonym
  • tool output..F. FAILED test_total - assert 0 == 42 1 failed, 3 passederror kept, text becomes a pseudonym
  • timestamps2026-10-01T18:56:48.510Z, 18:57:02.020Zdropped; only the duration is kept

The copy you send

The same call in events.jsonl, after profiler-client prepare.

  • workflowh:6e16c6b4…
  • workflow_version2.1.0
  • run_idh:9d3a9875…
  • event_typetool_call
  • nodeBash: python -m pytest
  • inputh:9f1e88cd…
  • input_completetrue
  • resulterror:h:591c93bb…
  • latency_ms13510
Kept as written h:… Pseudonym: a keyed hash, equal values match, nobody can reverse it without your key dropped Dropped: never written to the copy

This is real output of profiler-client on a synthetic coding-agent session, abridged. Point at a line to find it on the other copy. Pseudonyms are shortened here; real ones are 64 hex characters.

What stays with you, and what we receive

The client only reads files you name. It never opens a network connection, and it refuses to write anything if a value fails its privacy check. Read how the client works, and which agent traces it reads.

Stays on your machine

  • Your original traces
  • Prompts, replies and your request text
  • Tool output text and file contents
  • Working directories and timestamps
  • The key that makes the pseudonyms

Reaches the profiler

As written

  • The agent's built-in tool names and well-known commands like git status
  • File types such as .py, public model ids, the agent's version
  • Token counts, durations, cost and stop reasons

As pseudonyms

  • Project, session and message ids
  • MCP and custom tool names, script names
  • Your own workflow, agent and step names, unless you choose to keep them
  • Every tool input and every tool output

The reduced copy does leave your machine, and counts and timings can still say something about your work. We don't claim it's anonymous. Each dataset gets a fresh key unless you choose to keep one, so two uploads can't be linked by default.

A small beta, by invitation

Real traces are accepted only after every launch check passes: security, privacy, deletion and legal. Until then, the beta is a waitlist.

How it works for a tester

  1. Get an invitation and accept the beta terms and privacy notice
  2. Install the client on your own machine
  3. Run prepare on the traces you choose
  4. Read the copy with inspect
  5. Send it with submit, which asks you to confirm first
  6. Read your report and tell us what was useful
  7. Delete your data whenever you want

What to expect

  • 5 to 10 testers for 30 days, free, no card.
  • For people building agents with traces they're allowed to share. Please don't send health, children's or personal finance data.
  • Findings are leads to check, not proven savings. Nothing is replayed yet.

Not in this beta

  • Replaying a change against past calls to prove it's safe
  • Automatic changes to your code
  • Single sign-on, billing or an uptime guarantee

Beta terms and privacy notice

This is a draft. It is reviewed by a lawyer before the first invitation, and you accept the final version before you send anything. The client you run on your own machine has its own terms.

Beta terms

Who runs it
The beta is run by [operator]. It is free, by invitation, lasts 30 days, and has no uptime or support guarantee.
What you may send
Only traces you are allowed to share. If they belong to your employer or your customers, get their permission first. Please don't send health, children's or personal finance data.
What the report is
Findings are leads to check, not promised savings. Nothing is replayed, and you decide what to change in your own code.
Fair use
Don't try to break, overload or get around the service's limits, and don't use it on data you don't control.
Problems
Report bugs and security problems to [contact email]. Security reports are handled first.
Ending
You or we can end your participation at any time. When the beta ends, we tell you by email and delete your data as the privacy notice says.
No warranty
The service is provided as is, without warranties, as far as the law allows.
Liability
[limit of liability, set in legal review]
Law and courts
[governing law and courts, set in legal review]

Privacy notice

Who is responsible
[operator] controls the data. Write to [contact email].
What we receive
The reduced copy you choose to send, as described above, the name, email and organization you give when you sign up, and, if you choose to give them, your answers to the feedback questions after a report. Never your original traces, prompts, tool output or pseudonym key.
What we use it for
To make your report and to write to you about the beta. We improve the profiler only from the reports and feedback you send us. It is not sold, not used for advertising and not used to train AI models.
Legal basis
We use your sign-up details and dataset to run the beta you asked to join, and your feedback answers because you chose to give them. [legal basis confirmed in legal review]
Where it is kept
On servers in the Netherlands, run by our hosting provider Railway. Only the people running the beta can open it.
Who else handles it
Railway hosts the service. The sign-up form's provider is named here when the form opens. Railway Corporation is a US company and may process data in the United States under its data processing agreement with us, which relies on the EU–US Data Privacy Framework or the EU standard contractual clauses. If your organization needs a data processing agreement with us, ask at [contact email].
Server logs
Railway keeps the service's access logs: the time, the page asked for, the result and your IP address. They never contain your dataset.
How long
Your dataset is deleted from our servers as soon as its analysis finishes. Your report is kept so you can read it again, until you delete it or the beta ends. Sign-up details and feedback answers are kept until the beta ends, or until you ask us to delete them.
Your rights
Ask to see, correct or delete your data, to limit or object to how we use it, or for a copy to take elsewhere, at [contact email]. We answer within 30 days. You can withdraw your consent to feedback at any time, and you can complain to the data protection authority where you live or work.
This page
No cookies, trackers or third-party scripts. Once you sign in, one cookie keeps you signed in, and it is removed when you sign out.

Join the beta

Leave your details and we'll write to you with an invitation and a short onboarding call. We read every request ourselves.

Join the beta