Why AI buyers want it
Agency archives cover many projects across industries and stacks, written by professional teams under real deadlines and real client feedback. That variety is what coding models need, and buyers look for breadth rather than one more web app. Ownership is the question to settle first, because most of the archive belongs to clients.
Think of a session musician's recordings. The artist owns the song, but with a signed release the session can be licensed and everyone gets paid.
Client code needs a rights decision before it needs a price
General information, not legal advice.
Repository access or a statement that the agency “built” the software does not answer the title question.
US copyright law starts with the author and allows ownership or individual rights to be transferred, but the details depend on the agreement and facts. 17 USC 201 addresses ownership and transfer Office of the Law Revision Counsel, US House of Representatives, (opens in a new tab). The Copyright Office’s works-made-for-hire circular describes employee work and certain commissioned works under a written agreement, and warns that the concept can have serious consequences US Copyright Office, (opens in a new tab). These are starting points for your own lawyer, not a conclusion about an agency project.
Use the matrix
| Project or component | Likely rights path | Evidence to locate | Review route |
|---|---|---|---|
| Agency internal tool | Agency ownership or assignment | Employment and contractor terms, repository history | Technical scan and title review |
| Agency product | Agency ownership, subject to components and contributors | Formation records, contributor assignments, component list | Title and open-source review |
| Client deliverable with express assignment | Client may own the relevant rights | Statement of work, master agreement, payment and assignment clauses | Client permission or exclude |
| Client deliverable with retained agency rights | Agency rights may be limited by confidentiality or use terms | Contract, NDA, client restrictions and scope | Your own lawyer reviews the exact license |
| Mixed repository | Different folders have different owners | Component map and agreement for each part | Split scope, carve out or obtain consent |
| Subcontractor contribution | Rights depend on the subcontractor agreement | Written assignment or work-made-for-hire language | Obtain missing rights or exclude |
| Unknown or disputed title | No safe assumption | Contract register and evidence log | Stop and ask your own lawyer |
“Likely” is intentional. The matrix helps you route evidence. It is not a legal finding.
What a client consent letter should answer
If a client owns or controls a project, a consent letter should identify the client and agency, name the repositories or data in scope, describe the permitted AI-training or evaluation use, state whether the permission is exclusive, address confidentiality and personal data, identify the term, and say how any proceeds are handled. It should be signed by someone who can bind the client. Do not copy a generic consent template into a contract without your own lawyer’s review.
Also check the edges. A client NDA can limit disclosure even when the agency owns some code. A vendor component can impose its own terms. A contractor may have written rights over a contribution. A repository can contain customer data or credentials that must be removed. The agency’s rights decision should cover the whole delivery, not only the files written by employees.
Worked fictional example
Fictional agency “Sample Studio” reviews three repositories:
| Repository | Evidence | Decision |
|---|---|---|
| Internal deployment tool | Employee assignments and no client material | Candidate, after Repo Check |
| Client portal | Agreement assigns deliverables to client | Request written client permission or exclude |
| Shared integration library | Agency code plus subcontractor module | Split the scope, verify subcontractor assignment and review components |
The studio should not present all three as one clean archive. It can prepare the internal tool while the other two follow separate evidence paths. A client consent letter can make a project reviewable, but it does not erase an NDA, privacy duty or third-party license.
Before the appraisal
Make a project list with the rights status, evidence reference, excluded paths and next owner. Keep client names, private code and contract text out of a public worksheet. Run Repo Check locally for the technical report. Use the Trust page to see how title evidence becomes part of an ownership pack. Then use the appraisal for a route estimate. The appraisal is not a substitute for the consent or contract review.
If the evidence cannot answer who can license a repository, mark it unresolved. A narrower, documented scope is more useful than a broad claim that later fails review.
What sets the price
- Internal tools and your own products first. They carry the cleanest title.
- Client code where the IP never transferred, per your contract.
- Client code with a signed consent letter.
- Full history, tests and reviews, as with any repo.
The estimate on this page prices an agency archive of client repos licensed with consent. Title decides whether a repo can be licensed at all, and a client share comes out of the proceeds.
What blocks a deal, and the fix
- Contracts that assign IP to the client
- A consent letter that offers the client a share of proceeds can help a client agree. You choose the share.
- Client NDAs covering the code
- Code under a client NDA needs the client's written release before it can be offered. We draft the request.
- Contractors without the right transfer wording
- Contributors sign a confirmation that meets their local formalities and names AI training as a field of use.
What owners overlook
- Title follows a ladder: internal tools, then your own products, then client code you still own, then client code with consent.
- Engineers between projects can build training tasks from your repos, a route that can pay more than the code alone.
Market evidence
- Founders who build training tasks for AI labs put the typical price at $200 to $2,000 per task built from real repos.Epoch AI, (opens in a new tab)
- Published licensing programs exclude any repo with a client claim, an NDA restriction or an unpaid contributor, and the owner gives warranties on title.Rightmark,
How a deal works
Appraise
Answer a few questions about your repositories. See what affects the price and whether an indicative range is available. No files, no access.About a minute
Verify title
Repo Check runs on your own machine and reports the contributor, license and secrets checks buyers look for. With your IP documents, that report becomes the ownership pack.Before any offer
Route
Each repo goes to the route that fits it: a non-exclusive standing-rate license, or training tasks for repos whose tests run.Sign and get paid
You approve the agreement and its scope. On code routes, signing covers future non-exclusive sales, and you can withdraw code that has not been licensed yet. We never hold your passwords. Transfers use scoped, revocable connections your admins approve, or exports.About 4 to 10 months from submission to first payment
Questions
Can we license code we built for a client?
Only if you kept the IP or the client consents in writing. Many agency contracts transfer IP on payment, and an unpaid invoice does not by itself give you the rights. We read your contracts and send consent letters for the repos worth licensing; take legal advice on anything unclear.
What do our clients get?
Whatever you agree with them. One structure is a share of your proceeds from their repos, paid when you are paid. You set the share; we put it in the consent letter.
Do we approve each sale, and do our clients?
You approve the agreement and its scope, and each client approves its repos through the consent letter. On code routes, signing covers future non-exclusive sales. You can withdraw any repo that has not been licensed yet.
What could our archive be worth?
Each repo is priced like any private repo, typically $150 to $1,500 per sale, and each further license pays again. The estimate on this page (30 repos at $310 to $1,500 each, per sale) comes to $9,300 to $44,000 at Medium confidence. Indicative estimate, not an offer.
Source: Rightmark,
Can the same repo be licensed more than once?
Yes. Code licenses are non-exclusive by default, so each repo can be licensed to several AI labs and you are paid on each sale. Exclusive deals need a separate signed agreement.
What do we warrant?
That you own each repo or have written permission to license it, with IP assignments from every contributor. On some code agreements the indemnity for ownership claims is uncapped, so leave out any repo whose title is in doubt.
Do you need access to our repositories?
Not for the appraisal. Repo Check runs on your own machine and you share only its report. We never hold your passwords.
