Uploader
Import a browser session HAR
Drop your HAR file here
Upload Chrome, Safari, or Firefox exports and preserve headers, cookies, and timing data.
Requests
148
Cookies
12
Headers
Auth
Scrape Automate Build
Give Traceminer a HAR file (a recording of a website's network traffic), and it reverse engineers the entire API in minutes.
Chat with the HAR to understand the site, find issues, scrape data, run API flows, and export results in any format, no official APIs required.
/api/v2/users/me
Core
42 ms
/oauth/token
Auth
106 ms
/api/v2/products?page=1
Cache
14 ms
/api/v2/cart/items
Write
84 ms
Uploader
Import a browser session HAR
Drop your HAR file here
Upload Chrome, Safari, or Firefox exports and preserve headers, cookies, and timing data.
Requests
148
Cookies
12
Headers
Auth
Choose mode
Turn one HAR into the workflow you need
Pick the mode that matches what you want to do next.
Chat with HAR
Explore flows, auth, retries, and edge cases.
Replay in sandbox
Re-run any captured request and see the real response.
Debug with HAR
Trace failures and inspect request-response behavior.
Chat with HAR
Assistant
Use Cases
Most tools hit a wall when your HAR grows large. TraceMiner is purpose-built for it — thousands of requests, megabytes of trace data, processed without truncation.
Curious how your favourite app actually works? Upload its HAR and ask TraceMiner anything — which APIs get called, what each returns, how auth flows, how data is paginated. The entire backend, laid bare.
TraceMiner infers API patterns from HAR responses and replays them in a sandboxed environment. Just say what you need — download the results or export a ready-to-run cURL or Python script.
Big HAR files break them
Generic LLMs hit context limits fast when the trace gets large
Important requests get lost
Long chains are dropped, compressed, or only partially read
They start making things up
Once context runs thin, answers can sound sure but be wrong
Handles full HAR size
Upload huge HAR files and TraceMiner keeps working without sweating
Pulls the exact signal
Finds the real flows, endpoints, auth steps, and failures inside the noise
Tells you when data is missing
If the trace did not capture something, it says so clearly instead of hallucinating
Drop the HAR, ask what broke, and TraceMiner surfaces the failing request, explains the root cause, and turns the flow into polished docs your team can use immediately.
A simpler flow: compare both traces, let TraceMiner isolate the split, and get a clear explanation of the request or state change that caused the failure.
Working vs failing
Trace comparison
Drop in both HAR files and TraceMiner lines up the real request chain so you can stop guessing where the break happened.
Root cause signal
Mismatch surfaced
Headers, cookies, redirects, anti-bot checks, payload changes, missing steps. The trace tells the story once the noise is removed.
Actionable output
Short path to fix
Instead of scrubbing thousands of requests by hand, you get a short path to the root cause and a concrete explanation you can act on immediately.
Working HAR
200 on callback
Non-working HAR
302 loop on callback
TraceMiner diff
mismatch isolatedBrowser automation makes an agent read a page like a human — slowly, expensively, and it breaks on every redesign. TraceMiner gives it the API underneath instead: the same calls the site makes, with auth already worked out.
Private endpoints that take months of manual reverse engineering are exposed in a few clicks. AI agents sweep your entire HAR — no matter the size — and filter exactly what you asked for. Payment flows, product catalogues, auth tokens — just tell the AI and it zeroes in.
The hard part of driving a site programmatically was never the request — it was the token refresh, the signed header, the cookie that expires mid-flow. TraceMiner reads the real chain out of the trace and tells you exactly what a call needs to succeed.
Run any request in an isolated sandbox before you build on it. Wrong headers? Expired cookie? Unexpected schema? You see the real response, not a guess — so the flow you hand your agent is one you have already watched return 200.
Plug the verified flows into Claude Code or any agent runtime and let it work the site directly — no headless browser, no brittle selectors, no per-page compute bill. Direct API calls are faster, cheaper, and they do not break the next time someone ships a CSS change.
What used to take an entire engineering sprint now takes minutes.
No API docs. No insider access. No months of manual tracing. Capture the session once and your agents work the site through its own API.
Answer the questions closed products never answer cleanly, like how much you spent, what changed in your account, or which requests power the dashboard you already use.
Capture a workflow once, expose the real request chain, and turn repetitive admin work into something your agent can actually execute.
Understand how a product really works, compare working and broken HARs, and isolate the exact request, cookie, or header that changed.
Pay as you go
Start from $2, top up whenever you need, and use credits at your own pace over the next 6 months.
Starter
~ 500K tokens · 1 credit = 100 tokens
Test the full workflow and see if TraceMiner earns a place in your stack.
Builder
~ 1M tokens · 1 credit = 100 tokens
A practical pack for regular analysis, debugging, and sandbox replay.
Operator
~ 3M tokens · 1 credit = 100 tokens
For heavier usage across repeated runs, multiple targets, and deeper iteration.
Ready to Start
The web was already speaking through its network layer. Capture the trace, let TraceMiner read it, and ship the thing that used to die behind closed APIs.
No. Export the HAR from your browser session and upload it as-is. TraceMiner reads the captured traffic and lets you ask for the flow, bug, or endpoint you care about.
That is exactly the problem TraceMiner is built for. It pulls signal out of thousands of requests and tells you clearly when something was never captured.
That is the main use case. TraceMiner gives you the real request chain — endpoints, headers, and auth — behind a flow, and you can replay it in the sandbox before handing it to Claude Code or any agent runtime. Direct API calls instead of a headless browser.