| Quick facts | |
|---|---|
| How it collects | Connects to 100+ tools and extracts automatically[1] |
| Pricing | No public price list |
| Payment | On delivery of the anonymized dataset to the buyer, typically 2–4 weeks |
| Key check | Your vendors’ API terms on AI training |
Section 1
What we could verify
- Mercor’s data page describes four steps — scope, connect, process, payout — with extraction from “100+ supported tools” including Slack, Microsoft Teams, Gmail, Outlook, Salesforce, GitHub, Google Drive, Confluence and Notion.[1]
- It says compensation is based on data volume, the tools connected and the depth of data; that there are no fees; that extraction and anonymization are fully automated; and that payment is issued by wire on delivery of the anonymized dataset to the buyer, typically within 2–4 weeks of signing.[1]
- Business Insider reported Mercor bidding against micro1 for at least one seller.[2]
Section 2
Mercor’s published terms
| Term | What Mercor publishes |
|---|---|
| Business model | Connects to a company’s software through 100+ supported tools, extracts and de-identifies workflow data, and licenses it to frontier labs[1] |
| Pricing | No public price list; compensation based on data volume, the tools connected and data depth |
| Who qualifies | Lists target industries including legal, healthcare, finance and insurance, professional services, manufacturing, retail, real estate and logistics |
| Payment | Wire transfer upon delivery of the anonymized dataset to the buyer, typically 2–4 weeks after signing |
| Ownership | Not stated on the program page |
| De-identification | Automated extraction and anonymization; states no lab or third-party vendor sees raw data and engineers do not manually review it |
| Seller fees | No fees; Mercor covers extraction, anonymization and transfer costs |
| How data is collected | OAuth-style connections to tools such as Slack, Microsoft Teams, Gmail, Outlook, Salesforce, GitHub, Google Drive, Confluence and Notion |
| Funding / budget | Not stated on the program page |
Section 3
What to settle before you sign
- Your vendors’ API terms. Slack’s API terms bar apps offered outside the developer’s organization from training an LLM on API data or bulk exporting messages[3]; Google’s Limited Use rules bar using Workspace user data to train generalized models[4]. Ask how the connector route is reconciled with each tool you would connect — or offer an administrator export instead.
- Payment trigger. Payment is on delivery to the *buyer*. Ask what happens if no lab takes the dataset.
- Ownership and term. Not stated on the page — get them in the agreement.
- Scope control. The page says “no data leaves your systems until you approve it.”[1] Ask to approve at the record-category level, not the tool level.
For the full list of terms that matter more than price, see the seller’s guide or run a draft through the offer review checklist.
Section 4
How it compares
See how Mercor sits against the other buyers on scope, pricing, payment and collection method in the buyer comparison. If you hold an offer from more than one, the comparison is where to start.
Frequently asked questions
Is Mercor’s data program legitimate?
How does Mercor pay for company data?
Is connecting Slack or Gmail to a data buyer allowed?
Should I use an advisor to sell data to Mercor?
References
Sourced from primary industry reports, government data, SEC filings, and peer-reviewed valuation research. Retrieved at time of publication.
- 1.Mercor — Mercor Data — Monetize your data — A buyer’s own description of its connector-based extraction, compensation basis and payment timing; read 16 November 2026 (read November 2026)
- 2.Business Insider — Micro1 is making a $1 billion bet on AI’s latest data craze — Seller interviews, the range micro1 says it pays, and a Gartner estimate of AI data spending, 26 October 2026 (2026)
- 3.Slack Technologies, LLC — Slack API Terms of Service — Effective 10 October 2025; applications offered outside the developer’s organization may not train an LLM on API data or bulk export messages (2025)
- 4.Google — Google Workspace user data and developer policy — Last updated 3 September 2026; the Limited Use rules bar using user data to train generalized AI/ML models (2026)