The waitlist and the marketplace

#For developers who use agents

Join with the email you want to be paid at. When a buyer asks for sessions like yours - a product your agents used, a language, a kind of work - we email you with what they want and what they pay.

You then pick sessions that match, redact them on your machine, review them and send the ones you choose. You are paid for the sessions the buyer accepts.

What we will ask of every seller:

• Ownership. You confirm the sessions are yours to license, not your employer's or a client's.
• Identity. Payouts go through a payments provider that verifies identity, one account per person.
• Real work. Sessions are checked for duplicates and for signs they were generated to be sold.

#For companies that build developer tools

Your product is used by agents every day, and you see only the API calls. Agent sessions show the rest: how the agent found your docs, which command it tried first, where it got stuck, why it switched to a competitor or gave up.

Join as a buyer to be offered sessions involving your product, and reports drawn from them. Because you hold the server side of every session, you can verify a session against your own logs before you pay for it.

#How we keep sessions genuine

• Buyers pay only for sessions they accept.
• Part of each payout is held for a few weeks.
• Sessions are checked against facts outside them: public commits, package versions that existed on that date, and, with the seller's consent, the vendor's own logs.
• Near-duplicate sessions across sellers are rejected.