Skip to content
selltraces
Theme

Get paid for the agent sessions you already have.

Redact on your machine, approve exactly what leaves, and keep 70% of net revenue when AI labs license your traces.

Read the quickstartSee a dry run

Paste this into Claude Code, Codex, Cursor, Gemini CLI or OpenCode. It installs the CLI and stops before anything is uploaded.

Help me set up selltraces so I can sell my anonymized coding-agent sessions.

1. Read https://selltraces.ai/SKILL.md and follow it.
2. Install the CLI:
   curl -fsSL https://selltraces.ai/install | bash
   Windows: irm https://selltraces.ai/install.ps1 | iex
3. Run "selltraces login" and show me the code to approve in my browser.
4. Run "selltraces eligibility" and explain anything I still need to do.
5. Walk me through choosing sources and projects, one question at a time.
6. Run "selltraces upload --dry-run" and summarize what would be sent.

Rules: never upload, accept terms, or approve projects for me. Ask me first, every time.
Your agent asks before every upload.

Works with the sessions your agents already save.

No background process and no editor plugin. The CLI reads these folders only when you run it.

  • Claude Code~/.claude/projects/**/*.jsonlFull transcripts with tool calls.
  • Codex CLI~/.codex/sessions/**/*.jsonlRollout files, one per session.
  • Cursorstate.vscdb (workspace storage)Best effort. Cursor changes its format often.
  • Gemini CLI~/.gemini/tmp/**/chats/*.jsonSaved chats per project.
  • OpenCode~/.local/share/opencode/storage/**Sessions, messages and parts.

Paths shown for macOS and Linux. Windows paths are in the sources guide.

Three commands between your history and a payout.

  1. Preview on your machine

    The CLI reads your sessions, redacts them locally, and reports counts and findings. Nothing is sent.

    selltraces upload --dry-run

  2. Approve the upload plan

    Pick sources and projects, mark anything private, add terms to block. Only approved traces upload.

    selltraces upload

  3. Get paid when it sells

    We scrub again, score, and list. When a dataset with your traces sells, 70% of its net revenue goes to contributors.

    selltraces status

See what would leave before anything does.

A dry run is the default first step. It prints counts, exclusions and redaction findings by kind. It never prints your content and never contacts the upload API.

Runs
Offline, on your machine
Shows
Counts, never content
Machine readable
--dry-run --json
Uploads
Zero, until you confirm
example output

Redaction runs twice. The first pass never leaves your laptop.

On your machinebefore upload

  • API keys and tokens for common providers, plus generic bearer and basic auth
  • Private keys, certificates and .env style secrets
  • Passwords inside connection strings and URLs
  • Email addresses, phone numbers and IP addresses
  • Your home path, username and machine name
  • Any term you add with selltraces block

sk-ant-api03-•••• becomes [REDACTED:api_key]

On our serversafter upload

  • A second scan with a larger rule set and entropy checks
  • Project paths replaced by your alias and a one-way hash
  • Traces that still look risky are rejected, not patched by hand
  • Near-duplicates and very short sessions are dropped

Raw traces are stored in private, encrypted storage. Only reviewed, scrubbed versions are packaged for buyers.

No redactor catches everything.

Pattern matching misses secrets in unusual formats, and it cannot judge whether code or a business detail is confidential. Only approve projects you have the right to share, and mark the rest private. Read the limits.

You get 70% of net revenue. Here is how the math works.

Labs license datasets, not single traces. When a dataset sells, its net revenue is split across the traces in it, weighted by size and quality. 70% of each trace's portion is yours. We keep 30% to run review, storage, sales and payouts.

Before anything sells, the CLI and dashboard show an estimate. It uses a placeholder model of about $1.20 gross for a long, high quality trace, scaled down for short or low scoring ones.

  • Many traces never sell

    Demand depends on what labs are buying.

  • Paid after the buyer pays

    No advances, no guaranteed minimum.

  • Unsold means removable

    Exclude unsold traces at any time.

selltraces

payout statement, example only

Dataset
refactor-sessions-03
Buyer
AI lab (licensed)
Your traces included
212
Their share of net revenue
$236.40
Platform (30%)
-$70.92
You receive (70%)
$165.48

Paid after the buyer's payment clears.
Estimates are not payouts.

Illustrative numbers. Real sale prices vary and are not guaranteed.

Why labs pay for real sessions.

Synthetic tasks are clean. Real work is not, and models need to learn from the mess.

Learning to recover

Failed commands, wrong guesses and the fix that followed. This is the signal that is hardest to fake.

Evaluation sets

Benchmarks built from tasks people actually asked agents to do, in real repositories.

Tool use in context

How developers chain reads, edits, searches and test runs, and when they stop the agent.

Questions people ask first.

More in the docs FAQ.

Am I allowed to sell traces from work projects?

Maybe not. Your employment agreement, client contracts or open source licenses may restrict it. You are responsible for only approving projects you have the right to share. When in doubt, mark the project private and it is never read.

What exactly gets uploaded?

Only traces from sources and projects you approved, after on-device redaction, as normalized JSONL: your messages, the agent's replies, tool calls and tool results. Raw folder paths are replaced with an alias and a hash. The dry run shows the plan first.

Who can upload?

At launch, uploads are open to US residents who are 18 or older and have accepted the contributor terms. Anyone, anywhere, can install the CLI and run the local preview.

How much will I make?

We do not know yet, and neither does anyone else. It depends on what labs buy and how your traces score. The estimate in the CLI is a placeholder model, not a quote. Some contributors will earn nothing.

Can I take traces back?

Yes, for unsold traces. Run selltraces exclude or use the dashboard and they leave future datasets. Licenses already granted to a buyer for a past sale cannot be pulled back, which the contributor terms explain.

Does anything run in the background?

No. There is no daemon, no file watcher and no editor extension. The CLI does work only when you run a command.

How are payouts sent?

You connect a payout account in the dashboard. Earnings become payable after the buyer's payment clears. We will publish the schedule and minimums in the dashboard before the first sale.

Run a dry run. Decide after.

The preview is free, local and takes about a minute. Nothing uploads until you approve the plan.

Or install it yourself

$ curl -fsSL https://selltraces.ai/install | bash

Installs one binary to ~/.selltraces/bin. Read the script first at selltraces.ai/install.