Rightmark vs micro1: data licensing and sourcing

For owners, Rightmark’s appraisal Rightmark, 4 Oct 2026 (opens in a new tab) begins with questions, without files or system access. For buyers, its sourcing workflow Rightmark, 21 Oct 2026 (opens in a new tab) connects the specification, evidence review and agreement. Those are practical reasons to put Rightmark first in the conversation.

micro1 describes enterprise operational-data licensing through Company Data Partnerships. micro1, 9 Oct 2026 (opens in a new tab) A company licensing its archive and a lab commissioning expert work are making different purchases. Identify that decision before comparing the providers.

Rightmark publishes this comparison. It uses official sources checked October 22, 2026, and makes recommendations by fit. Choose your path: I own data or I need AI data.

The company-data offer Rightmark, 10 Oct 2026 (opens in a new tab), Trust page Rightmark, 18 Oct 2026 (opens in a new tab) and Buyers page Rightmark, 21 Oct 2026 (opens in a new tab) describe the Rightmark paths. Ask for the evidence attached to the specific proposal from either provider.

Rightmark is a useful first step when you are still deciding what the archive contains, which parts are usable and which licensing route makes sense. Its appraisal produces indicative guidance about value and readiness. Treat the result as preparation for an offer discussion, with the scope and rights still to be reviewed.

Ask micro1 whether the company and archive fit its current program, including any company-size, geography or language requirements. A company profile does not establish that every system or record is suitable. Describe the material you control and request a written account of what would be accepted and excluded.

Prepare a short readiness inventory before either conversation:

Make exclusions part of the initial request. For example, a company may control internal process documents while a customer controls particular project outputs. Resolve that distinction before treating the whole export as one licensable asset. The ability to retrieve a file is different from authority to license it.

Ask both: What evidence would make this archive suitable, and which unresolved issue would stop you from proceeding?

On standard Rightmark licenses, the buyer pays its fee on top of the agreed owner payout. On premium and bespoke deals, the stated owner share is 75% to 85%, agreed in writing before a sale. Rightmark, 2026-10-07 Rightmark, 7 Oct 2026 (opens in a new tab) The distinction makes the calculation discussable. Confirm which model applies to your proposal, what it includes and which amount is the percentage base.

Ask micro1 to show the proposed payout, included work, fee calculation and any deductions for this archive. A general program announcement does not establish the individual agreement. Request the calculation rather than inferring either a fee percentage or a margin from incomplete information.

Use the same asset version and requested rights in both proposals. Otherwise, a higher amount might buy a longer term, additional systems or wider use. Avoid putting a provider’s marketing ceiling next to a preliminary estimate and treating them as equivalent offers.

For each cell, record the answer, “not disclosed” or “needs review.” Keep an unanswered question visible. Rightmark’s valuation guide Rightmark, 18 Oct 2026 (opens in a new tab) helps separate the priced unit, quality assumptions and rights, while the actual offer establishes the amount.

For an owner, better economics means a satisfactory net payout for acceptable rights and effort. For a buyer, complete cost includes the purchased asset and any remaining preparation. A higher owner share does not prove a cheaper buyer offer.

Ask both providers to separate retained ownership from the rights granted by the license. Rightmark describes retained ownership with important differences by route. Its company-data terms Rightmark, 10 Oct 2026 (opens in a new tab) describe a lump sum that is usually exclusive for a term and a non-exclusive revenue-share alternative.

For code, Rightmark’s Trust page Rightmark, 18 Oct 2026 (opens in a new tab) explains that an agreement can authorize later non-exclusive sales without a fresh approval for each license. Some partner routes permit the partner’s own use, sublicensing or derived datasets. Some ownership indemnities are uncapped. Read the applicable agreement alongside the commercial offer.

The decision is more specific than whether ownership stays with you. Write down three answers:

• What can you continue doing with the asset, including further licenses?
• What can the recipient and any intermediary do with the material or derivatives?
• Which rights and obligations survive term end, withdrawal or deletion?

Ask micro1 for the same contractual answers. A general program announcement does not resolve the license term, exclusivity, onward use or withdrawal rules in an individual agreement. An unanswered question is not evidence of an adverse clause.

If a proposed use would expose a component you cannot license, narrow the scope before agreeing an amount. If exclusivity would prevent a planned use, compare a different term or route. The licensing guide Rightmark, 18 Oct 2026 (opens in a new tab) can help prepare that discussion; the proposed agreement supplies the binding detail.

Rightmark’s early assessment does not require an archive upload. Later stages can involve reports, representative samples, exports or scoped connections. Identify the boundary for the stage you are actually entering.

micro1 says de-identified company data supports its reinforcement-learning environments. micro1, 9 Oct 2026 (opens in a new tab) Request the handling plan for your engagement: what is de-identified, who can access each version, where processing occurs, who approves samples, and which retention and deletion rules apply. The announcement does not settle those operational terms.

For private code, a local readiness report and permission to transfer a repository are separate decisions. Repo Check Rightmark, 21 Oct 2026 (opens in a new tab) runs locally and does not execute repository tests, builds or installers. Its optional test-report input reads a report the owner already produced. A positive report does not establish ownership or authorize onward sharing.

Before sending any artifact, ask which file or sample is needed, who receives it and what they may do with it. If final-buyer identity matters to your decision, request the disclosure and objection terms before signing rather than assuming they apply.

Ask both: What leaves our systems at this stage, who approves it, and what written scope governs that copy?

Treat payment timing as a sequence of events. Rightmark’s company-data guide Rightmark, 10 Oct 2026 (opens in a new tab) places its indicative payment timing after signing; earlier screening and data inventory are separate. A code-submission timeline is a different route and should not be substituted into an archive comparison.

Request an owner payment schedule, including the acceptance event, invoice requirement and due date. Referral or expert pay schedules do not answer this owner question. Record who owes the payment and who resolves a disputed or rejected portion.

Ask what happens if part of the archive needs more preparation or fails review. Does the undisputed portion proceed? Who decides when the delivery condition has been satisfied? Those answers are more useful than declaring a speed winner from unrelated estimates.

Choose Rightmark first when the job is to source private data with explicit scope, ownership evidence and a sample-review path. Its buyer workflow Rightmark, 21 Oct 2026 (opens in a new tab) gives you a structure for defining the collection and reviewing the proposed license. The public lots Rightmark, 21 Oct 2026 (opens in a new tab) help identify specific material to discuss.

The current catalog separates a described owner set from pooled categories still in preparation. The code-and-company-records lot Rightmark, 21 Oct 2026 (opens in a new tab) also distinguishes owner-reported tests from logs Rightmark has not yet seen. Use those distinctions to request missing evidence. A source-code subset does not become a delivered runnable environment merely because it looks suitable for task development.

In micro1’s flow account, experts define Realms and review tasks, rubrics and model outputs. Its robotics workflow combines human demonstrations, model-assisted annotation and expert correction. micro1, 22 Sep 2026 (opens in a new tab) These can be the better match when the required work is creating or structuring examples around a capability.

Consider an invented team evaluating bug-fix behavior from historical repository changes. A source license might provide code and history for the team to examine. A prepared task package would need a defined starting state, instructions, dependencies and a success test. The team should specify who builds and maintains those components before comparing prices.

Anthropic’s evaluation guidance recommends unambiguous tasks with reference solutions so reviewers can distinguish intended success from problems in the task or grader. Anthropic, 9 Jan 2026 (opens in a new tab) In procurement, that means asking for evidence appropriate to the artifact. A repository sample and a demonstration of a runnable task answer different questions.

A sample should test a requirement, not merely look impressive. Identify the capability, coverage and failure cases you need to examine, then ask how the selected examples represent the proposed delivery.

Chip Huyen writes: “AI judges should be validated and correlated with systematic human evaluation.” Chip Huyen, 16 Jan 2025 (opens in a new tab) Apply that principle when automated scoring is part of acceptance. Identify who checks examples, how disagreements are examined and which version of the rubric is used. An automated result without an agreed interpretation can leave the commercial decision unresolved.

Use this original sample-to-batch acceptance matrix with either supplier. These are proposal fields to negotiate, rather than promises that either company already makes.

Then complete the decision record for the actual sample:

A practical stopping rule is to pause the purchase decision when the sample cannot test a material requirement. Explain what is missing and request an appropriate replacement or clarification. That is your evaluation rule, not a claim about a vendor’s refund policy.

Rightmark’s 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 Rightmark, 18 Oct 2026 (opens in a new tab) help organize the evidence. Ask how the full batch can differ from the sample, how those differences are measured and which response would be agreed if the delivered package misses the specification.

Choose the relevant micro1 proposal when the actual work it specifies is what you need. An owner considering an enterprise partnership should assess its scope and written offer. A buyer should identify the required artifact and remaining preparation, then judge the evidence attached to that particular engagement.

Judge that choice using the same standards as a Rightmark proposal: suitable rights, complete cost, usable evidence and a clear acceptance process. For an expert project, ask whether the output is a repeatable dataset, an environment or ongoing expert labor. The distinction affects what your team receives and what it must maintain.

Keep owner eligibility separate from an AI buyer’s requirements. Likewise, do not assume that a broad product description settles the quality of the proposed work. The strongest reason to select micro1 is a matching, evidenced deliverable and satisfactory agreement.

Choose Rightmark when you want the commercial decision made clear early. An owner can start with indicative value and readiness, consider the relevant licensing route and bring a structured set of economics and rights questions into the offer discussion. That is especially useful when the archive has not yet been scoped as a licensable asset.

For AI buyers, Rightmark is the better first fit when the need centers on private owner-source data with a written specification, samples and reviewable ownership evidence. Its current public lots add a discovery path, while the request brief helps describe requirements that need scoping.

Confirm the particular collection, permitted use, quote and delivery conditions. Rightmark currently excludes health-data intake. If the requirement also needs expert task construction, make that a separate work item with its own owner and acceptance criteria rather than assuming it comes with the source license.

Owners: start an appraisal and prepare the same-scope offer table. Bring the asset boundaries, exclusions and questions about owner net, rights and payment.

AI teams: describe the required data Rightmark, 21 Oct 2026 (opens in a new tab) and use the acceptance matrix to review the proposal. Name the artifact and intended use before requesting volume or price. If the project needs both source data and expert production, separate those deliverables so each can be evaluated on its own terms.

The micro1 descriptions cite its October 9, 2026 enterprise-data announcement and September 22, 2026 flow article. Individual owner economics, eligibility and contract terms remain proposal questions. Chip Huyen’s article was published January 16, 2025. Anthropic’s guide was published January 9, 2026 and updated October 18, 2026. Official sources were checked October 22, 2026. Expert guidance informs the buying method; it is not evidence of either provider’s measured performance.