Rightmark vs Mercor: data licensing and sourcing

Owners can begin through a questions-only appraisal Rightmark, 4 Oct 2026 (opens in a new tab). Buyers can use the sourcing workflow Rightmark, 21 Oct 2026 (opens in a new tab) to define the required collection and evaluation. Rightmark’s value is a clear path from an initial question to a scoped, evidence-backed commercial decision.

Mercor’s dated publications describe expert-built data, evaluations and agent-improvement work. Mercor, 8 Oct 2026 (opens in a new tab) For an owner proposal, compare the actual scope, responsibilities, payout and agreement. For an AI-data purchase, compare the artifact and work included behind the company name.

Rightmark publishes this comparison, based on official sources checked October 22, 2026. Choose the relevant path: I own data or I need AI data.

Use Rightmark’s Trust page Rightmark, 18 Oct 2026 (opens in a new tab) and buyer workflow Rightmark, 21 Oct 2026 (opens in a new tab) to examine its route. Apply the same proposal questions to both companies. A missing public term is a question to resolve, rather than proof of an unfavorable policy.

Rightmark’s appraisal helps organize the commercial question before a technical handoff. Describe the archive, its coverage and the systems involved to obtain indicative guidance about value and likely routes. You can then decide which parts to explore and what must remain excluded. The appraisal itself does not require files or system access.

Ask Mercor to map the proposed workflow for your archive. Establish which systems would connect, what leaves them, who prepares the data and which approval is required before each transfer. The written scope should name exclusions and the person authorized to approve each step.

Make each provider describe the stages separately:

Ask both: What leaves my systems before I approve the agreement and scope? Follow that with a request for the authorization that applies at each later stage. An initial estimate and a final delivery should not quietly become the same permission.

Rightmark’s company-data page Rightmark, 10 Oct 2026 (opens in a new tab) helps frame the archive route. Before the offer discussion, identify the person who can authorize the license, the systems under that authority and the exclusions. If buyer identity matters to your decision, ask what can be disclosed and agreed before signing.

Ask Mercor to itemize extraction, de-identification, transfer and other preparation in the proposal. Identify which costs are included, separately charged or deducted, then compare the written owner amount for equivalent rights. These are offer questions, not assumptions that Mercor charges any particular fee.

Rightmark states that buyers cover extraction, scrubbing and transfer. Standard licenses add its fee to the buyer price without reducing the agreed owner payout; premium and bespoke deals give owners 75% to 85%, agreed in writing before a sale. Rightmark, 2026-10-07 Rightmark, 7 Oct 2026 (opens in a new tab)

A published fee model, by itself, does not establish which proposal leaves you with more money for equivalent rights. A fee paid on top remains part of the buyer’s total spend. An agreed owner amount can be satisfactory even when the buyer total is not disclosed, but the missing total cannot be used to calculate a retained percentage.

Start with the same licensed asset, version, use and term, then complete the owner side of this cost, responsibility and trigger sheet. Leave unknowns visible as “not disclosed” or “needs review.”

Use the last column to explain why an unanswered term matters. An unclear preparation responsibility might create work for your team; an unclear payment trigger might affect when you can rely on proceeds. The sheet does not assume either cost exists. It makes the proposal answer the question.

Rightmark’s valuation guide Rightmark, 18 Oct 2026 (opens in a new tab) helps compare the unit, evidence and licensed scope. A better owner offer is the combination of net proceeds, acceptable rights and manageable obligations, rather than a claim inferred from a fee label.

Ask for the payment method, contractual trigger, acceptance conditions and due date. Separate an indicative processing estimate from the event that makes payment due under the agreement. Record who owes the payment and how a disputed portion would be handled.

Rightmark’s company-data guide Rightmark, 10 Oct 2026 (opens in a new tab) describes indicative timing after signing, with screening and data inventory earlier in the process. Compare those stages explicitly. A source-code submission has its own route and should not be used as an archive payment comparison.

For each proposed deal, record:

Ask what happens if a subset is rejected, a transfer is delayed or a review finds a rights issue. Which portion can proceed, and who decides? The resulting schedule is more useful for planning than comparing two headline ranges with different starting events. Put any binding deadline in the agreement.

Ask who approves extraction, sample sharing and final delivery, and record each permission separately. Approval to move a defined copy still needs a clear account of what the recipient may do afterward. Do not assume that the same approval covers every stage.

Rightmark’s Trust page Rightmark, 18 Oct 2026 (opens in a new tab) makes route differences explicit. Company-archive lump sums are usually exclusive for a term; non-exclusive revenue share is another route. Code agreements can cover later non-exclusive sales without a fresh approval each time. Some partner arrangements allow their own use, sublicensing or derived datasets, and some ownership indemnities are uncapped.

Put those terms beside the commercial benefits. Retaining ownership does not answer how long the recipient may use the copy, whether others may use derivatives or what remains after withdrawal. Ask Mercor for the proposed agreement and the same answers rather than inferring detailed rights from a general company description.

For each data handoff, record the authorized copy, recipient, purpose and version. Then ask:

• Which access can we revoke, and what happens to copies already licensed?
• Which onward uses and derived materials are permitted?
• What do deletion and retention obligations cover?
• What ownership or permission promises are we making?
• Which review evidence corresponds to the package being delivered?

Use the licensing guide Rightmark, 18 Oct 2026 (opens in a new tab) for preparation. If an unresolved right affects a component, narrow or pause that component before treating it as part of the priced archive. A transfer method does not settle the authority to license the content.

Rightmark is our preferred starting point for private owner-source data with an explicit specification, sample evaluation and ownership evidence. The buyer workflow Rightmark, 21 Oct 2026 (opens in a new tab) helps you define the requirement and review the proposed collection. The public catalog Rightmark, 21 Oct 2026 (opens in a new tab) can also surface material worth examining.

Its currently described code-and-company-records set Rightmark, 21 Oct 2026 (opens in a new tab) includes outstanding evidence checks. Owner-reported test runs are distinguished from logs Rightmark has not seen. Other pooled concepts remain in preparation. Use the public description to decide what to request; confirm the actual scope and readiness in the proposal.

Mercor describes experts creating evaluations and training data around real work. Mercor, 8 Oct 2026 (opens in a new tab) Its agent-development article describes expert-defined criteria, evaluation feedback and forward-deployed engineering. Mercor, 4 Sep 2026 (opens in a new tab) A dated APEX-Agents release documents benchmark tasks and grading changes. Mercor, 8 Sep 2026 (opens in a new tab) These are different deliverables from a source archive. Ask which are included in the commercial proposal and what your team would still need to prepare.

Write down what your team needs to receive before discussing price. Is it material to build on, a task package to run, additional expert judgments or an ongoing evaluation service? Then identify what your own team will still construct, review and maintain.

A source-data proposal may be attractive because you control the downstream design. A prepared package may be attractive because the needed construction is already included. Compare the work left on your side, the evidence you can inspect and the permissions needed for the intended use.

Ask both providers what can be evaluated before commitment. The meaningful distinction is which sample tests the actual requirement and which deliverable the agreement covers.

A lower quote can cover less work. Before selecting a supplier, make preparation and acceptance explicit enough that the two offers can be compared.

Anthropic’s evaluation guide recommends clear task instructions and reference solutions, with grading that tests the intended success condition. Ambiguous tasks or misconfigured graders can otherwise distort the result. Anthropic, 9 Jan 2026 (opens in a new tab) Its authors are Mikaela Grace, Jeremy Hadfield, Rodrigo Olivares and Jiri De Jonghe. This informs the review method below; it does not certify either provider’s output.

Use this buyer extension of the responsibility sheet:

For an original fictional example, imagine a company evaluating support-resolution tasks from a privacy-filtered archive. Its rubric requires the customer’s original email address, but that field was deliberately removed from the sample. The required answer and the permitted data conflict.

The buyer should resolve which behavior is actually being evaluated and align the sample, task and rubric before judging the model. Request a corrected specification or permitted evidence, not an unsupported assumption that the missing address can be recovered. This scenario is invented; it is not a finding about Rightmark or Mercor.

For a source archive, the equivalent discipline is checking that the sample contains the relationships and coverage your intended use needs. Define the full-batch checks as well. A clean sample cannot establish that every delivered record will meet the same standard.

Complete these fields before committing:

Rightmark’s buyer 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) provide a starting structure. Ask each supplier to explain how the sample can differ from delivery and which response would be agreed if the package fails acceptance. The worksheet requests terms; it does not create a vendor guarantee.

Consider Mercor when its actual owner proposal satisfies your scope, responsibility, payout and rights requirements. Compare the work assigned to your team and the payment conditions alongside the amount. A useful comparison depends on the agreement offered for your archive.

For AI teams, a matching expert-data or evaluation proposal can be a strong reason to choose Mercor. Request the specific package, supporting evidence and remaining work. If it removes work your team would otherwise perform, include that work in the cost comparison.

The decision should rest on the proposed deliverable and terms, rather than assuming every supplier sells the same thing. Keep public availability or timing claims separate from the commitment made for your order. That allows Mercor’s relevant strengths to count without turning them into a universal performance claim.

Choose Rightmark when the first task is to make the owner’s asset and commercial options understandable. Its appraisal and route explanations give you a practical way to discuss readiness, rights and written economics before committing the archive. The owner sheet then makes the offer comparable on what you keep and what you grant.

For AI buyers, choose Rightmark when private source data is the central need and the decision requires specification, samples and ownership evidence. Current public lots add a discovery path, and the request brief helps turn a broad need into something a supplier can scope.

Confirm that the actual collection, rights, price and preparation fit. Rightmark currently excludes health-data intake. If the project also requires task construction or ongoing evaluation, specify that work separately with its own responsibilities and acceptance evidence.

Owners: appraise the archive, then use the cost, responsibility and trigger sheet to compare written offers. Establish the asset, net amount, rights and payment event together. If an introducer is involved, ask how it is compensated; Rightmark’s Scout terms Rightmark, 14 Oct 2026 (opens in a new tab) set out its attribution, payment and conflict rules.

AI buyers: describe your requirement Rightmark, 21 Oct 2026 (opens in a new tab), including the artifact, intended use, required evidence and acceptance method. Review a specific proposal against that requirement. For private-data sourcing and licensing that needs clear economics and a reviewable path to agreement, start with Rightmark.

Mercor descriptions cite its October 8, 2026 research account, September 4, 2026 agent-development article and September 8, 2026 APEX-Agents release. These describe capabilities, not standard owner economics, handling or payment terms. Anthropic’s guide was published January 9, 2026 and updated October 18, 2026. Official sources were checked October 22, 2026. The comparison does not claim independently measured payouts, delivery speed or model results.