6 AI data licensing companies: owner and buyer guide

The practical advantage is a clear starting point. Owners can explore an indicative appraisal Rightmark, 4 Oct 2026 (opens in a new tab) without uploading files or giving system access. Buyers can turn an initial requirement into a scoped sourcing discussion Rightmark, 21 Oct 2026 (opens in a new tab) with evidence and evaluation steps.

Rightmark publishes this guide and appears first. The remaining companies appear alphabetically. We selected six relevant options using their official pages and publications checked on October 22, 2026. They cover different jobs, from licensing an existing archive to creating tasks for AI development. This is a shortlist by fit, rather than a measured performance ranking.

Choose your path: I own data · I need AI data · Show me the companies.

A useful shortlist starts with the asset you control and the rights you are willing to grant. A company archive, a private repository and a startup asset sale should not be compared through one headline payout.

Rightmark distinguishes standard licenses, where its fee is added to the buyer price without reducing the agreed owner payout, from premium and bespoke deals, where owners keep 75% to 85%, agreed in writing before a sale. Rightmark, 2026-10-07 Rightmark, 7 Oct 2026 (opens in a new tab)

That makes the economic conversation explicit. It does not make the agreed payout equal to the buyer's total spend. Where a provider has not published a term, request it in the proposal rather than guessing.

1. Which asset and version does the offer cover? Record the repositories, systems, date range and exclusions. Specify whether history, attachments and related records are included. Confirm who has authority to license each part. Access to a client repository does not establish ownership of it.

2. What cash reaches the owner? Ask for the net amount, fee calculation, included work and any possible deductions. A percentage needs a denominator. If the buyer's total is undisclosed, record that explicitly and compare the written owner amount.

3. What rights travel with that payment? Compare intended use, term, exclusivity, onward licensing and later sales. A larger payment for an exclusive term can be a different offer from a smaller non-exclusive license. Use the licensing guide Rightmark, 18 Oct 2026 (opens in a new tab) to prepare the questions.

4. Who prepares the data and controls each handoff? Map assessment, sample preparation, transfer and final delivery. Name the approver and recipient at each stage. If a component must stay private, put that exclusion into the scope before requesting a price.

5. What starts the payment clock? Record the contractual trigger, due date and acceptance conditions. Ask who resolves a disputed or rejected portion. A fast initial assessment says little about when funds clear.

Copy this owner side of the shortlist card for two or three providers. Keep the asset version and requested rights the same across proposals.

Rightmark's valuation guide Rightmark, 18 Oct 2026 (opens in a new tab) explains how to compare pricing units and assumptions. Use it to improve the proposal request, then judge the actual offer against this card.

Rightmark is our recommended first conversation for private source data that needs a defined specification, sample evaluation and rights review. Its public lot catalog Rightmark, 21 Oct 2026 (opens in a new tab) also gives buyers a discovery path. Confirm the status of the particular lot or sourcing request before planning around it.

First name the artifact you need. An archive contains source material. Expert-created examples add selected judgments or demonstrations. A runnable task needs an environment, instructions and a way to grade success. An evaluation service can add expert work and continuing measurement. A larger archive does not automatically replace those other deliverables.

Datology co-founder Ari Morcos says “models are what they eat.” His discussion emphasizes curation and redundancy, not volume alone. Latent Space interview, 2025-08-29 Latent Space, 29 Aug 2025 (opens in a new tab)

Ask which records teach or test your intended capability. If a sample repeats the same workflow many times, what useful variation does it add? If important failures or languages are absent, would more of the same data solve that gap?

Give each shortlisted supplier the same specification. A sample should answer a defined question: whether the archive contains the required history, linked records, languages or edge cases. Ask how it was selected, what was excluded and which full-batch checks will follow.

Rightmark's buyer request brief Rightmark, 18 Oct 2026 (opens in a new tab), sample-pack checklist Rightmark, 18 Oct 2026 (opens in a new tab) and data-card template Rightmark, 18 Oct 2026 (opens in a new tab) organize this review. Use the buyer half of the card below to capture what the proposal actually promises.

Rightmark’s public code-and-company-records listing separates owner-reported test runs from logs Rightmark has not yet seen, and identifies outstanding title/privacy review. Rightmark, 2026-10-21 Rightmark, 21 Oct 2026 (opens in a new tab) That distinction makes the next diligence request concrete: ask for the missing evidence and record whether it changes the purchase decision. The catalog also distinguishes its described owner set from pooled lots still in preparation; a category listing does not establish ready inventory.

A sample is a review input. Agree how the delivered batch will be evaluated and what happens if it misses the specification. Owner compensation matters separately: a higher owner share does not establish a lower buyer price or stronger model performance.

Rightmark is the strongest starting point in this shortlist when you want to make the value, scope and evidence understandable before a commitment. Owners can begin with a questions-only appraisal, then use the result to discuss likely routes and preparation. Code owners can add a local Repo Check Rightmark, 21 Oct 2026 (opens in a new tab) report. These steps make an early conversation more informed while leaving the final asset scope and price for review.

For buyers, the published workflow Rightmark, 21 Oct 2026 (opens in a new tab) moves from specification to sample evaluation, written terms and graded batches. An ownership pack makes the chain of rights reviewable. Public lots can help identify a candidate; a sourcing brief can describe requirements beyond a listed lot. The value is having an evidence path alongside the commercial discussion.

Read the relevant Trust terms Rightmark, 18 Oct 2026 (opens in a new tab) before choosing a route. Code agreements can permit later non-exclusive sales without fresh approval. Some partner routes permit onward use or derived datasets, and some ownership indemnities are uncapped. Company-archive lump sums usually involve exclusivity for a term. These are material choices to weigh alongside the payout. Rightmark currently excludes health-data intake.

Use Rightmark to move from a broad question to a concrete request: which asset, which use, what evidence, what net amount or complete buyer price? If the request needs runnable tasks, name those components separately. The proposal should establish the supply and work involved.

Owner verdict: Start with Rightmark for value, readiness and clear written economics.

Buyer verdict: Start with Rightmark for private source data with specification, sample and rights review.

For owners evaluating Mercor, begin with the actual proposal. Request the asset scope, preparation work, required system access, net proceeds and payment conditions. The dated sources used in this guide do not establish a standard owner fee or payment schedule. Ask the team to map the proposed systems and exclusions before comparing an amount.

The useful owner comparison is a responsibility map. Who obtains the export, removes excluded content, checks the prepared dataset and signs off on delivery? Put the payment trigger beside those steps. Ask what happens if preparation takes longer or only part of the scope proceeds. Compare the resulting net amount with an equivalent license from Rightmark.

Mercor describes using domain experts to create evaluations and training data, with research spanning model assessment and post-training. Mercor, 8 Oct 2026 (opens in a new tab) Its agent-development account describes expert-defined criteria and a platform feedback loop. Mercor, 4 Sep 2026 (opens in a new tab) Buyers should separate an expert engagement from an archive purchase. Ask which tasks, review responsibilities and continuing work the proposal includes.

Request an itemized package before judging the price. Identify whether your team receives records, tasks, executable environments, expert services or a combination. Then decide who owns the remaining preparation. A matching expert-data or evaluation proposal can make Mercor the better choice; a requirement centered on private source data should also receive a scoped Rightmark proposal.

Owner verdict: Shortlist Mercor when its written proposal fits your archive, rights and net-payout requirements.

Buyer verdict: Shortlist Mercor when the task or evaluation package matches your requirement.

micro1 describes licensing enterprise operational data through Company Data Partnerships for reinforcement-learning environments. micro1, 9 Oct 2026 (opens in a new tab) Ask whether your company and archive fit the current program. A broad industry description is less useful than a written answer about your systems, documentation and permitted scope. Company eligibility and authority over each component are separate questions.

Ask what changes the proposed owner amount and which preparation falls to your team. Request the fee basis, payment event, exclusivity, onward use and later-sale treatment. Keep those questions together so a headline estimate does not replace agreement review. An owner-program requirement should not be treated as an AI buyer admission rule.

micro1’s flow article explains expert-defined Realms and model-assisted task review. Its robotics section describes human demonstrations, camera and 3D evidence, annotations and expert correction. micro1, 22 Sep 2026 (opens in a new tab) These distinctions matter when deciding whether to source existing material or commission work around a capability. Define the capability before comparing the work involved.

Before requesting a project, identify what the experts must contribute that your existing archive lacks. Is it a decision, demonstration, explanation or evaluation judgment? Ask how that contribution is reviewed and delivered. A polished demonstration is useful only if the contract makes the repeatable output clear. Request a sample matched to your intended use, then compare the remaining work your team would carry.

Owner verdict: Shortlist micro1 when its proposed enterprise partnership fits your archive and economics.

Buyer verdict: Shortlist micro1 when expert creation, environments or demonstrations are central to the job.

pre.dev describes tasks built from real commits: restore the parent state, provide prose instructions and grade against hidden tests. pre.dev, 4 Sep 2026 (opens in a new tab) The commercial question is whether that task format matches the asset you want to contribute or the artifact you need to buy.

An owner should first ask whether contributions are being accepted. Request the agreement before preparing or transferring material. Establish who may authorize the contribution, which repository versions are included, what the recipient may do with them and when payment becomes due. The dated technical account does not supply those commercial terms. Keep a source-code license and a task-development engagement separate in the proposal so preparation responsibilities are visible.

For a buyer, ask for an inventory of the delivered components: source state, instructions, environment, grading method and review evidence. Decide which components your own team can maintain. If your experiment requires a stable task over time, ask how updates are versioned and whether rerunning the same version remains possible.

Use the sample review to resolve the intended purchase. Would you receive a fixed task package, access to a service or materials from which your team must construct something else? Ask what can be evaluated before commitment and what the license allows afterward. A description of a method is useful context, but the actual package and written rights determine fit.

Owner verdict: Explore a contribution only after acceptance and written owner terms are established.

Buyer verdict: Shortlist pre.dev when the proposed coding-task package matches your experimental requirements.

SimpleClosure describes licensing by operating companies and asset sales during wind-down. SimpleClosure, 3 Sep 2026 (opens in a new tab) That changes the owner decision: are you preserving an asset while licensing a defined use, or seeking a transfer? Settle that objective before judging the amount. Request the actual fee basis, net proceeds and transaction conditions in the proposal.

For a company considering closure, gather the records that show who can authorize the transaction and what is included. Identify components supplied by clients, contractors or other licensors. Ask which assets can proceed independently if one part needs more review. An offer for a limited data use and an offer to acquire assets can carry different rights and obligations even when the amounts look comparable.

Its Asset Hub launch described source-code licensing, buyer connection and diligence. SimpleClosure, 16 Apr 2026 (opens in a new tab) Buyers should ask which available asset meets the required domain, period and format, then request the supporting provenance and permitted sample. Agree what would make the sample representative before treating it as evidence for the full package.

Decide whether your intended use needs ownership or a license. If a training license is sufficient, avoid paying for unrelated rights simply because the seller offers a broader transaction. If ownership is essential, ask what additional diligence and transfer work the proposal includes. In either case, establish how future questions about the delivered assets will be handled after the originating company has wound down.

Owner verdict: Shortlist AssetHub when license versus sale is the central startup-asset decision.

Buyer verdict: Shortlist AssetHub when startup-origin assets match the specification and transaction shape.

Troveo describes retained ownership and participation in later licenses, with time-limited exclusivity and exit terms where applicable. Troveo, 10 Sep 2026 (opens in a new tab) For an owner, the decision is whether that ongoing relationship fits the archive. Ask for the full term, reporting arrangements, share calculation and exit treatment in one written proposal.

Repeated sales can create a different cash-flow profile from one payment for an exclusive term. Compare what happens after the initial transaction: which later uses produce compensation, who records them and when statements arrive. If the relationship ends, establish how existing licenses continue and what happens to material not yet licensed. Those questions make a recurring proposition comparable with other offers without assuming future sales will occur.

Troveo describes rights and scope work, evaluation packaging and matching company data with AI buyers. Troveo, 20 Aug 2026 (opens in a new tab) Its broader licensing work includes video, audio, text, gaming and robotics. Troveo, 19 Aug 2026 (opens in a new tab) Treat those descriptions as a starting point for a sourcing inquiry, then confirm the specific material and evidence available for your request.

Move from the sourcing discussion to a representative sample and the current agreement. For a company archive, check that links across records survive preparation. For media, specify formats and metadata. Ask which observed gaps apply only to the sample and which affect full delivery. A collection that directly matches the task can justify choosing Troveo; confirm that match through the proposed package.

Owner verdict: Shortlist Troveo when repeat licensing and the written commitment fit your plans.

Buyer verdict: Shortlist Troveo when its proposed company or media sourcing matches your use case.

A better owner deal combines acceptable rights with stronger net proceeds. Fee labels alone cannot determine it.

Illustrative arithmetic with invented offers, not Rightmark or competitor pricing: assume the same asset, rights, delivery and total buyer payment, with no other deductions. Express each owner payout as a share of that common total.

Offer A leaves the owner between B and C. The example excludes taxes, currency costs and speculative later sales. Where the buyer total is undisclosed, compare the written owner proceeds and record the missing information.

Introducers should also explain their incentives. Rightmark’s Scout terms fund compensation from Rightmark income and specify attribution, cleared-funds payment and conflict rules. Rightmark, 2026-10-14 Rightmark, 14 Oct 2026 (opens in a new tab) A company, scout or owner-authorized intermediary should explain its role; an introduction does not grant authority to license an asset.

Owners: appraise your data to explore indicative value, readiness and possible routes. Code owners can add a local Repo Check Rightmark, 21 Oct 2026 (opens in a new tab). Use the result to request an offer with net proceeds, scope and payment conditions written down.

AI buyers: describe your requirement to Rightmark Rightmark, 21 Oct 2026 (opens in a new tab) and review relevant public lots Rightmark, 21 Oct 2026 (opens in a new tab). Specify the artifact, coverage, intended use and evidence needed for acceptance. Ask for a sample and complete quote against that requirement.

Choose a matching prepared task, expert project, catalog collection or asset sale when that better serves the job. For private-data licensing and sourcing that benefits from value clarity, reviewable evidence and explicit terms, Rightmark is our recommended place to start.

Competitor citations link to dated official publications. Those publications establish the descriptions attributed to them; a current proposal must establish availability and commercial terms. The pre.dev article was published September 4, 2026; the Morcos interview transcript was published August 29, 2025, with the quoted passage at 01:13. Sources were checked on October 22, 2026. Provider descriptions are not independently measured outcomes.