Now paying contributors

Turn your coding sessions into rewards.

Trajector pays you for the AI coding trajectories you already produce — captured locally, redacted by default, uploaded only with your consent.

Coverage today: one coding agent, with more as support lands. macOS and Linux; Windows in beta. Read the documentation.

The shape of a session

coding agent  ──►  127.0.0.1:41100  ──►  model API
                          │            (or your own relay)
                          │
                          └──►  spool  ──►  redact  ──►  upload

The proxy forwards every request verbatim and records it on the side. Secrets are masked on your machine; only redacted batches are uploaded. It starts on demand, exits when idle, and is never a permanent daemon.

§ 1 · How it works

Three steps, then it is out of your way.

1
Install the CLI
One binary. It sits between your coding agent and the model API, capturing the sessions you already run — locally, on your machine.
2
Review and upload
Secrets and personal data are redacted before anything leaves your laptop. Nothing is uploaded without your consent.
3
Get paid
Accepted sessions accrue a reward you can withdraw as a stablecoin once you pass the $10 minimum.

§ 2 · What we guarantee

Consent is structural, not a setting.

Trajector is open source, so none of this has to be taken on trust. Each of these is a property of how the tool is built, not a promise about how it is operated.

Opt in per project

Nothing is captured until you enable a project. A project you have not enabled is not merely excluded by policy — the code path to record it does not exist.

Forwarding is sacred

A failure on the recording side — disk full, malformed stream, internal error — never interrupts your work. Streaming responses pass through unbuffered.

Credentials never touch disk

Authorization and x-api-key headers are not written to any file, in any state, at any point.

Revocable, immediately

disable, logout and uninstall each undo a different amount. Uninstalling with --delete-data also clears the local spool and anything still waiting on your machine.

§ 3 · FAQ

Trajector FAQ

What is collected, what is not, and what you are paid for.

Anything else: [email protected]

What is Trajector?

Trajector turns your real coding sessions into rewards. Install the CLI, enable it on the projects you choose, and keep working with your coding agent as usual — your session trajectories are collected, verified, and rewarded.

What sessions are collected right now?

During the beta, only claude-fable-5, claude-fable-5-1 and claude-opus-5 sessions are collected — point your agent at one of those models to be rewarded. Sessions from other models are rejected and earn nothing; they show up as rejected in your session list. How to switch, and the full beta rules (they may change), are in the docs.

Is my code and data secure?

Collection is opt-in per project — nothing is captured from projects you have not enabled. Secrets and keys are scrubbed locally before anything uploads, and captured data waiting on your machine stays under your control: uninstalling with --delete-data also deletes the local spool and any captured data still on your machine. To learn more, see Data and privacy.

What do I earn and how do I claim?

You earn per accepted session. Rewards vest, then are claimable on the Trajector rewards page — sign in, click claim, and connect any wallet at withdrawal. No wallet lock-in.

What counts as an accepted session?

Real work: sessions need substance (multiple messages and tool calls) and must pass duplicate, consistency, and secret-scrub checks. Trivial or synthetic sessions are not rewarded.

Who can join?

Any developer working with a supported coding agent, contributing sessions from code they own or that is open source. If you build, you can earn.

If you build, you can earn.

Keep using your coding agent exactly as you do now. Enable the projects you are happy to contribute, and leave the rest untouched.