A software company sells its data to AI by licensing its private repositories and the engineering history around them, to a buyer like Mercor or micro1.
Mercor pays software companies $50,000 to $500,000 for the code. micro1 pays $100,000 to over $3 million for the documentation, tickets and workflows around it.
Those are two different products from the same company. Most teams can sell both.
For the full process across every industry, start with our guide to how to sell your company’s data to AI companies.
Key takeaways
- Mercor’s software company listing pays $50,000 to $500,000 and wants private repos with three or more years of commits from at least 10 engineers.
- It asks for 50,000 or more lines the company owns outright, written by people, with tests that run.
- Code that was ever public, mirrored or open-sourced is out. So are forks, single-author repos and code mostly written by AI tools.
- micro1 buys the other half: source code documentation, engineering workflows, bug tracking, product planning and knowledge bases, from $100,000 to over $3 million.
- Retired products and codebases from acquisitions qualify, which makes a wound-down startup a seller.
- A contractor who wrote your code still owns it unless they signed an assignment. Software isn’t a work made for hire by default.
- License Exception ENC doesn’t let you release encryption source code to a national of an embargoed country, wherever they sit.
What code and engineering data do AI companies buy?
Mercor’s software company listing, read November 9, 2026, splits it like this:
| Data | Mercor’s view | Main risk |
|---|---|---|
| Git history with branches and diffs | Core of the license | Secrets in old commits |
| Pull requests and code reviews | Core of the license | Customer names in review threads |
| Test suites and CI configuration | Core of the license | Credentials in pipeline config |
| Linked tickets and engineering docs | Core of the license | Customer emails and support detail in Jira |
| Thousands of PRs with review discussion | Adds to what you earn | Personal data about your own staff |
| Design docs, runbooks and postmortems | Adds to what you earn | Named incidents and affected customers |
| C, C++, Rust, Swift, Kotlin, Ruby, COBOL or .NET | Adds to what you earn | Vendored third-party source |
| Banking, insurance, healthcare, trading or blockchain code | Adds to what you earn | Regulated data in fixtures, export rules on crypto |
| Code that was ever public or open-sourced | Not a fit | Rejected outright |
| Forks, single-author repos, mostly AI-written code | Not a fit | Rejected outright |
| Client work an agency doesn’t own | Not a fit | Rejected outright |
The bar is specific: three or more years of commits from at least 10 engineers, 50,000 or more lines the company owns outright, and tests that still run.
History that mostly predates 2025 is worth more. So is openness to an exclusive license on part of the code.
Mercor names the companies it wants: B2B SaaS, fintech, marketplaces, developer tools, healthtech, and internal platform teams at companies that don’t sell software at all.
Live products, retired products and codebases from acquisitions all qualify, as long as the code has never been public. It works with exports from GitHub, GitLab, Bitbucket, Jira, Linear and Confluence.
How much is software company data worth to AI?
| Listing or program | Company earns | Size bar |
|---|---|---|
| micro1 data partnership | $100,000 to $3 million and up | 30 or more full-time staff |
| Mercor: cybersecurity company | $20,000 to $750,000 | 20 to 2,000 employees |
| Mercor: software company | $50,000 to $500,000 | 15 to 500 employees |
| Mercor: AI product company | $20,000 to $480,000 | 5 to 200 employees |
| Mercor: SaaS and subscription | $55,000 to $350,000 | 50 to 1,000, with a data team |
Read the rows as four products, not four prices. Mercor’s software listing buys the code; its SaaS listing buys your product databases, warehouse and analytics code; its AI product listing buys real usage data from an AI app or agent.
micro1 buys none of those. Its data partnerships page asks for source code documentation, engineering workflows, bug tracking, product planning and technical knowledge bases, and it also licenses agent trajectories for $1 million to $2 million a year.
Mercor shows a $35,000 referral fee on the software listing, which is paid to whoever refers the company. Its cybersecurity listing pays the company less at the floor and far more at the top, so a security product company should read both.
Our guide to how much company data is worth to AI compares published payouts across industries.
Does open-source code in your repo kill the deal?
GPL-2.0 section 2(b) is the clause to understand. Any work you distribute that contains or derives from GPL code has to be licensed as a whole, free of charge, under the same terms.
Whether handing a dataset to an AI buyer counts as distribution is a question for your counsel. The practical move is to find the code first, then decide.
- Generate a software bill of materials in SPDX format for every repo in scope
- Run a license scan over the working tree and the history, since a file deleted in 2021 is still in the git history you’re selling
- List every copyleft license you find: GPL, LGPL, AGPL, MPL
- Separate real dependencies from code someone pasted in
- Exclude the contaminated paths, or swap them before you scope the deal
Also check whether any of this code has been published before. Mercor asks directly, and a repo that was mirrored to a public account for a week is no longer private data.
Who owns the code, you, your client or your contractor?
Software is the clearest case of a rule that catches people out. Under 17 U.S.C. 101, a commissioned work counts as made for hire only in nine listed categories, and software isn’t one of them.
So a contractor’s code belongs to the contractor until a signed assignment moves it. 17 U.S.C. 204(a) makes that signature the whole requirement.
Check four things before you scope a repo.
- Employee agreements. An invention assignment clause covers work your staff did in their jobs, under 17 U.S.C. 201(b).
- Contractor agreements. A signed assignment, not an invoice. Contractors from a decade ago are the usual gap.
- Customer statements of work. Custom integrations and bespoke modules are often assigned to the customer who paid for them.
- Source escrow and audit clauses. An escrow agreement doesn’t block a license, but it tells you which customers think they have rights in the code.
Acquired codebases need the same check twice over. Read the asset purchase agreement and confirm the IP actually transferred, including contractor-written parts.
What has to come out before you ship?
| Item | What to do |
|---|---|
| API keys, tokens and passwords | Rotate them, then remove from the history, not just the working tree |
| Test fixtures and seed data from production | Replace with synthetic records; real customer rows are personal data |
| Database dumps checked in years ago | Find them in the history and strip them out |
| Customer names in PRs, tickets and postmortems | Replace with consistent codes across every repo |
| Your engineers’ names and emails in commits | Pseudonymize consistently, or get consent; this is personal data |
| Screenshots and logs pasted into design docs | Review by hand; redaction tools miss images |
| Vendored third-party source | Exclude the paths, or confirm the license allows it |
| Internal hostnames and infrastructure config | Generalize, or cut |
Commit metadata is the part teams forget. Every commit carries a name, an email address and a timestamp, so the history is a record of your staff’s working hours.
Mercor says it signs an NDA, scopes the data and runs the export, removing or protecting personal information. Have an engineer on your side read a sample anyway.
Our guide to anonymizing data for AI training covers the tools and the standards.
Do export controls apply to your code?
15 CFR 740.17 sets out License Exception ENC for encryption commodities, software and technology classified under ECCNs 5A002, 5B002, 5D002 and 5E002.
The limit sits in the same paragraph. ENC doesn’t authorize export to, or transfer in, any country in Country Group E:1 or E:2, or the release of source code or technology to any national of those countries.
That last clause is the one that matters here. A reviewer sitting in a third country still counts, which is why the question to ask a buyer is who touches the data and where.
Ask for a clause that excludes controlled technology from the license. Most buyers will take it, because it costs them one directory.
Our guide to selling cybersecurity data to AI covers the intrusion-software controls, which are a separate problem with the same shape.
Who buys code and engineering data?
- Mercor: git history, pull requests, tests, CI config and linked docs, for companies of 15 to 500 people with three or more years of commits. Pays $50,000 to $500,000.
- micro1: source code documentation, engineering workflows, bug tracking, product planning and technical knowledge bases, for companies with 30 or more full-time staff. Pays $100,000 to over $3 million, and prefers US companies and data in English. You can apply to micro1 here.
- SimpleClosure AssetHub: aimed at companies winding down, which is where a dead product’s codebase still has value.
A shut-down startup is a real seller here. Mercor takes codebases from retired products and acquisitions, and micro1’s referral terms pay more for a defunct company’s data than a live one’s.
Don’t sign an exclusive on the whole estate first. Mercor rules out data already licensed exclusively through a broker, and the two buyers want different slices of the same repo.
Our list of companies that buy business data for AI has each buyer’s terms.
What are the steps for a software company, start to finish?
- Inventory the private repos. Engineers who committed, years of history, lines of code, languages, and whether the tests run.
- Check what has been public. Mirrors, old open-source releases and public gists all disqualify code.
- Run a license scan. Working tree and history, with an SPDX bill of materials for each repo.
- Confirm ownership. Employee assignments, contractor assignments, customer statements of work, acquisition paperwork.
- Apply to both buyers. Mercor for the code, micro1 for the docs, tickets and workflows. They aren’t competing for the same files.
- Rotate and scrub secrets. Rotate first, because publishing a scrubbed history doesn’t un-leak a key that’s already out.
- Screen for encryption controls. Classify anything implementing cryptography before it goes in scope.
- Have counsel review the license. Our AI data licensing agreement checklist covers exclusivity, derivative models and deletion.
- Test a sample. Have someone try to name a customer, or find a live credential, in 50 exported commits.
Start with a retired product. Nobody is shipping from it, the secrets are long since rotated, and it proves the pipeline before you scope your main repo.
Common mistakes when selling software company data to AI
The most common mistake is scoping a repo before checking what’s in its history. These are the others:
- Scrubbing the working tree and leaving keys and dumps in old commits
- Removing secrets without rotating them first
- Offering a repo that was public or mirrored at some point
- Forgetting that a contractor’s code stayed the contractor’s without a signed assignment
- Including custom modules a customer’s statement of work assigned to them
- Shipping test fixtures built from a production database
- Treating commit names and emails as metadata rather than personal data
- Pitching only Mercor, when micro1 buys the documentation side separately
- Reading the $35,000 referral fee as what the company gets paid
Frequently asked questions
Can a software company sell its source code to AI companies?
Yes, if the code is private and the company owns it. Mercor’s software listing wants private repos with three or more years of commits from at least 10 engineers, and pays $50,000 to $500,000.
How much do AI companies pay for source code?
Mercor publishes $50,000 to $500,000, with more for large codebases or exclusive terms. micro1 publishes $100,000 to $500,000 for a qualified partnership and over $3 million for data nothing else matches.
Does open-source code in the repo disqualify you?
Forks and copies of open-source projects are out. Vendored copyleft code creates obligations under licenses like GPL-2.0 section 2(b), so run a license scan over the history and exclude those paths.
Who owns code a contractor wrote for you?
The contractor, unless they signed an assignment. Software isn’t one of the nine commissioned categories in 17 U.S.C. 101, and 17 U.S.C. 204(a) means a transfer needs a signed writing.
Can a shut-down startup sell its codebase to AI companies?
Yes. Mercor takes codebases from retired products and acquisitions as long as the code was never public, and micro1’s referral terms pay more for a defunct company’s data than a live one’s.
Do export controls apply to selling code?
They can, for cryptography. License Exception ENC in 15 CFR 740.17 covers encryption software and technology but doesn’t authorize releasing source code to a national of a Country Group E:1 or E:2 country.
Last updated: November 9, 2026
Disclosure: some links on this page are affiliate links. If you sign up through one, we earn a commission at no extra cost to you.
This isn’t legal advice. Have counsel review your contracts and any data license, and your export control lead review anything implementing cryptography, before you sign.






