A marketplace for coding-agent data

Sell the agent sessions you already run. Buy datasets you can trust.

Real coding-agent trajectories — collected from Claude Code, Codex, Hermes and OpenClaw, redacted at the source, proven from the actual bytes, and held in encrypted escrow until a sale clears.

What a dataset actually is

Not synthetic prompts — a real session, tool calls and all.

checkout-refactor.atf.jsonATF · formatVersion 2
session_start  claude-code · repo: checkout-svc
turn-1         "Fix the failing checkout total test."
llm_call       claude-sonnet-5 · 2,481 tokens
tool_call      run_tests   → exit 1  totals.test.ts:112 failed
tool_call      edit_file   → src/cart/total.ts  (rounding fix)
tool_call      run_tests   → exit 0  34 passed
verification   suite green · 1 file changed

Every listing carries the real event stream — turn structure, tool inputs and observations, model usage. Buyers see morphology and a bounded transcript preview before they pay.

01 — Collected, not synthesized

From the harnesses you already run

A resident collector converts finished Claude Code, Codex, Hermes and OpenClaw sessions into portable traces — no instrumentation, no SDK, no change to your agents.

02 — Proven from the bytes

The seller can't fake the numbers

The registry recomputes hashes, event counts, and morphology from the actual dataset. What buyers evaluate is measured server-side, not self-reported.

03 — Encrypted at publish

A storage breach yields nothing

The full dataset is validated and credential-scanned, then envelope-encrypted with a per-dataset AES-256-GCM key wrapped in the database — key material never sits beside the ciphertext.

04 — Fail-closed release

Decrypts only for the buyer

The dataset is released to the entitled buyer only after the sale is confirmed. Every other request — before release, wrong account — fails closed.

How escrow works

Full data at publish. Cleartext never leaves.

Sellers upload the whole dataset when they list. The registry validates it in the clear, proves it, then keeps only ciphertext.

STEP 1

Validate & prove

Hardened intake: bomb/traversal defense, ATF schema check, per-trace hashing, and a credential scan. Proof — sample, counts, hashes — is computed from the bytes.

STEP 2

Encrypt & custody

A random per-dataset key encrypts the archive; the key is wrapped by a master key held in the database. Only ciphertext lands in object storage.

STEP 3

Release on sale

After the operator confirms payment, the entitled buyer streams a decrypted download. Objects are deleted after the retention window.

Get in early.

We're onboarding a small group of sellers and buyers during the private beta. Tell us which side you're on.

Request early access →