Publish a dataset

Five steps take the canonical seller ATF source from a raw session into encrypted registry escrow and a public metadata listing.

Get approved as a seller

Request access; an operator reviews it and issues your seller API key. Anyone can browse — only approved sellers publish.

Install the CLI and sign in

Authenticate the CLI with your web account using the passwordless device-code login.

bash

trajectory auth login --registry $REGISTRY_URL

Collect a session into a trace

Turn a real coding-agent session into an ATF trace, then confirm it is marketplace-ready.

bash

trajectory collect watch --out ./collected --once
trajectory inspect --trace ./collected/<runtime>/<session>.atf.json --json

Publish the dataset

Publishing sends application/vnd.trajectory-escrow-upload as an always-on encrypted length-prefixed envelope: [uint32 BE candidate JSON length][candidate JSON UTF-8][dataset zip]. Repeat --trace to bundle several traces; the --candidate JSON carries buyer-facing narrative only. JSON-only candidate publishing is retired and rejected.

bash

TRAJECTORY_REGISTRY_API_KEY=$SELLER_KEY \
  trajectory marketplace seller candidate publish \
  --registry $REGISTRY_URL \
  --candidate ./candidate.json \
  --trace ./collected/<runtime>/<session>.atf.json --json

Commit to binding terms (optional)

Promote the candidate to a binding commitment (reserve, delivery SLA, consequences) so it can accept binding bids.

bash

TRAJECTORY_REGISTRY_API_KEY=$SELLER_KEY trajectory marketplace seller commitment submit --registry $REGISTRY_URL --fixture ./commitment.json --json

Proof from the bytesThe registry derives the legacy bounded redacted proof preview and aggregate-only/content-free evidence from the canonical ATF bytes. It stores ciphertext plus metadata, never public plaintext; key material never sits beside the object.