Directory context is the existing public description. Every contractual field is an open question; no company-specific term or payout has been verified.
| Review topic | Mercor | micro1 | Scale AI | Turing |
|---|---|---|---|---|
| Directory context | Data monetization and professional workflow data.Directory description · verify current program | Data partnerships and expert human data for AI development.Directory description · verify current program | Data infrastructure, evaluation, and AI development services.Directory description · verify current program | AI development and human data services.Directory description · verify current program |
| Permitted use | Not verifiedAsk what training, evaluation or other uses are permitted. | Not verifiedAsk what training, evaluation or other uses are permitted. | Not verifiedAsk what training, evaluation or other uses are permitted. | Not verifiedAsk what training, evaluation or other uses are permitted. |
| Exclusivity | Not verifiedAsk whether other licenses remain possible. | Not verifiedAsk whether other licenses remain possible. | Not verifiedAsk whether other licenses remain possible. | Not verifiedAsk whether other licenses remain possible. |
| Acceptance | Not verifiedAsk what evidence completes acceptance. | Not verifiedAsk what evidence completes acceptance. | Not verifiedAsk what evidence completes acceptance. | Not verifiedAsk what evidence completes acceptance. |
| Payment | Not verifiedAsk about amount, conditions and timing. | Not verifiedAsk about amount, conditions and timing. | Not verifiedAsk about amount, conditions and timing. | Not verifiedAsk about amount, conditions and timing. |
| Handling | Not verifiedAsk who prepares, reviews, transfers and retains data. | Not verifiedAsk who prepares, reviews, transfers and retains data. | Not verifiedAsk who prepares, reviews, transfers and retains data. | Not verifiedAsk who prepares, reviews, transfers and retains data. |
Choose companies and topics to shape your review.
Make the proposals comparable
Begin with the same archive description for every company you compare. Record the systems, categories, history, approximate volume, and known exclusions. If one proposal covers support tickets and another includes the entire company archive, their prices do not describe equivalent opportunities. Keep those differences visible rather than reducing both proposals to a single amount or an unsupported ranking of which buyer pays more.
The comparison controls let you choose companies and topics, but the table deliberately distinguishes directory context from unverified terms. Public positioning can help you organize research. It cannot establish exclusivity, acceptance, payment, or handling requirements for a specific transaction. Replace an unknown only when you have a clear source or a direct answer tied to the exact scope under discussion.
Understand the rights being requested
Ask what the receiving party would be allowed to do, who could receive the material, and how long those rights would last. Consider whether the proposed use is narrowly defined or permits several activities. Then examine exclusivity: does it restrict the same dataset, a broader category of records, or future arrangements? The wording and scope matter more than a simple exclusive or nonexclusive label.
Keep potential changes to the archive in mind. A proposal concerning existing records may raise different questions from one that includes continuing access or future additions. Identify which version is actually on the table. Write a short plain-language explanation of the requested rights and have the relevant reviewers check it against the proposed agreement. Do not rely on a comparison checkbox to summarize an ambiguous contractual clause.
Compare the operational burden
Preparation can involve identifying the authorized records, removing excluded material, explaining structure, preserving context, and checking the result. Ask which party performs each task and what evidence shows it is complete. A proposal that requires extensive preparation by your team can have a different practical value from one covering a smaller, already understood scope. Keep that work visible alongside the proposed commercial terms.
Acceptance needs its own definition. Clarify what the reviewer tests, how long the review takes, what happens if material is rejected, and how changes are approved. Delivery, receipt, and acceptance are separate milestones. Record whether payment depends on one or more of them. These questions do not presume any company’s terms; they help you identify the points that a useful proposal must eventually answer.
−Preparation effort hidden
−Acceptance left unresolved
+Duties clearly assigned
+Payment conditions understood
Keep evidence beside the conclusion
For each proposal, retain the source, date, scope, and version. Record who supplied the answer and which questions remain open. If a later conversation changes the price or requested rights, keep the earlier version rather than overwriting it without explanation. This makes the final decision easier to review and helps avoid treating an early indication of interest as a firm, complete agreement.
Use a short decision note to explain the tradeoffs that matter to your company. Those may include preparation effort, permitted use, future licensing options, review obligations, or payment conditions. The best outcome is a decision you can explain from the evidence, not a table with every cell filled. This preview sends no comparison to buyers and does not negotiate or approve terms on your behalf.
- 01Retain each versionSource and date
- 02Explain the tradeoffsScope and effort
- 03Document the conclusionOpen questions preserved