Reinforcement learning environments

Licensing RL environments and task sets

Last updated /Reinforcement learning environments

Licensing an RL environment is a grant of uses, not a feeling that you bought 'the AI.' The paper should say what is licensed, whether anyone else may get the same package, which uses are in, and what happens to the seed data and the copies. This page lists the questions. It does not draft the clauses and it is not legal advice. Take them to your counsel.

The buying guide is how to buy RL environments and task sets. The pillar is reinforcement learning environments: what they are and what real work adds. The spec is an RL environment requirements template. The test before you pay is acceptance testing an RL environment. The seed is seed data privacy in RL environments. Questions for counsel about training data in general, not this environment form, are questions buyers should ask counsel before a training license.

Terms grid comparing exclusive and non-exclusive environment deals, labeled Buyer guide
A grid of exclusive and non-exclusive questions. Not clauses, and not a price.

What is actually licensed

Separate the environment runtime, the task set, the grader, the seed data, and any replica of an application. A license to run a sandbox is not a license to the company's records inside it. A license to the tasks is not a license to ship the model you train. Ask which of those objects the grant covers. If the draft says 'the environment' and never lists them, you do not yet know what you are buying.

Terms grid comparing exclusive and non-exclusive environment deals, labeled Buyer guide
A grid of exclusive and non-exclusive questions. Not clauses, and not a price.

Exclusive vs non-exclusive

Exclusive means the seller does not grant the same package to others for the uses you named. Non-exclusive means they may. Epoch AI's FAQ reports that two environment founders, independently, described exclusive deals as roughly four to five times the price of non-exclusive ones: https://epoch.ai/gradient-updates/state-of-rl-envs . That multiple is their interview report, not a rule and not our price. The grid on this page asks the question. It does not fill in a fee.

Ask what 'the same package' means. A near copy with the names changed can defeat a sloppy exclusive. Ask how long the exclusive lasts and what you can show as proof.

Permitted uses: RL, evals and SFT trajectories

Reinforcement learning, evaluation, and supervised fine-tuning on solved trajectories are different uses. A right to evaluate is not a right to train. A right to train is not a right to publish the traces. Write the verbs you need. Do not accept 'all AI uses' because a demo was convincing.

Rights in seed data and replicas

If the seed came from a real company, the environment vendor may not have had the right to grant your use. Ask what shows that they could: their contract with the owner, and what that contract allows them to pass on. A replica of a commercial application can have a separate set of limits. Do not assume the sandbox license covers the software it imitates.

Updates and maintenance

Tasks go stale and graders get patched. Ask who may ship an update, whether you must take it, and whether an update can change the task you accepted. A silent replacement is a different dataset. Maintenance is not the same sentence as the grant of use.

Term and termination

Ask when the permission ends, what must be deleted, and which affiliates and subprocessors may touch the slice. Copies in backups and logs are part of that question. We will not choose your term or write the deletion sentence. Counsel does. We do not negotiate your legal position.

Bring the spec and the acceptance notes to the same meeting as the draft. A license that grants a use your spec marked out of scope, or that skips a cheat your sample already failed, is not a document to sign because the demo was impressive. Pause is available. Impatience is not a term, and a passed sample is not a grant. If two drafts disagree, you do not have one position.

  • Which objects are in the grant.
  • Exclusive or not, and for which uses.
  • Training, evaluation, and traces, each named or absent.
  • Seed and replica rights, updates, and the end of the term.

A passed acceptance test is not this review. Keep both checklists.

Questions buyers ask

Will you draft the license?

No. These are questions for your counsel. We will not supply clause text.

Is exclusive always worth the multiple?

Epoch's interviewees described a multiple. They did not say you should pay it. Ask what you are keeping from others.

Does a right to evaluate include training?

Do not assume it. If the verb is missing, treat it as missing until counsel says otherwise.

Can the vendor pass on someone else's records?

Only if their own grant allows it. Their signature does not repair a missing upstream right.

Is the grid on the image a term sheet?

No. It is a picture of the comparison. It is not paper you can sign.

Does this replace the buyer rights checklist?

No. That checklist is the general training-data questions. This page is the environment-shaped list. Use both. Neither is advice.

Describe the data you need

Tell us the use, the records, and the limits. A request is not a promise that a matching dataset is available.

Tell us what data you need