Who actually pays?
The contracting licensee, marketplace or intermediary may differ from the AI developer using the data. Verify the entity responsible for payment in the offer.
Explore buyers, marketplaces and intermediaries through their published programmes. Compare the route, the available payment evidence and the questions to resolve.
Sources and guidance · Reviewed October 2026The contracting licensee, marketplace or intermediary may differ from the AI developer using the data. Verify the entity responsible for payment in the offer.
Programmes describe different records, formats and rights requirements. These filters identify research leads from published descriptions; they do not establish eligibility.
A published range is an indication from its provider, not a quote. Request the scope, acceptance rules, timing, deductions and rights with any amount.
Explore price evidence →25 programmes
Records mentioned: Procedures and knowledge bases; Approval and escalation histories; Support and CRM workflows; Finance and ERP records; Contracts and procurement records; Data warehouse records.
Appen agrees commercial terms before extraction and pays on acceptance. Its program says preparation and transfer are covered without deductions from seller compensation.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Appen enterprise data program ↗Records mentioned: Workplace chat; Email and calendar history; Documents and revisions; Project and support records; CRM and sales activity; Finance records and code history.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Avelence licensing process ↗Avelence enterprise data partnerships ↗Records mentioned: Email and chat archives; Meeting transcripts; Documents and wikis; Support tickets; CRM and project histories; Engineering and warehouse exports.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Corpus licensing process ↗Corpus enterprise archive program ↗Records mentioned: Private code repositories; Development history and tests; Raw data ZIP bundles; Enterprise documents and logs; HUD tasksets with RL environments.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
DataVendor seller guide ↗DataVendor codebase estimator ↗HUD codebase sales guide, June 2026 ↗Records mentioned: Audio datasets; Video datasets; Images; Text collections; Multimodal data; Code and technical datasets.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Defined.ai partnership programs ↗Records mentioned: CRM notes; Support tickets; Email threads; Internal knowledge bases; Industrial and sensor records; Other sector-specific datasets.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
FileYield catalog and seller workflow ↗Records mentioned: Code repositories; Specialized offline content; Large high-quality datasets.
Invited owners negotiate payment for delivered offline content. Google describes a non-exclusive arrangement with retained IP; expressing interest does not guarantee an invitation.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Google Content Offer Pilot ↗Records mentioned: Process documentation; Project histories; Engineering specifications and tests; Logistics and production records; Research workflows; Financial and administrative workflows.
The company-data program promotes this earnings range. Eligibility, scope and commercial review determine any actual offer; the headline is not a record of completed sales.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Handshake AI data partnerships ↗Handshake company referral eligibility ↗Records mentioned: Codebases; De-identified business data; Operational history for training environments.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
idler founder announcement and company profile at Y Combinator ↗Records mentioned: Enterprise code and review history; Operational workflows and tickets; Recorded calls and meetings; Factory-floor video; Clinical archives.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
LH2 institutional data sourcing ↗Records mentioned: Procedures and knowledge bases; Email, calendar and chat; Support and CRM records; Finance and project histories; Code and design files.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
License My Data current company-record requirements ↗Records mentioned: Slack and Teams records; Email and metadata; Documents and wikis; CRM activity; Code, commits and issues; Sector-specific operational records.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Mercor enterprise data program ↗Records mentioned: SOPs and playbooks; Internal knowledge bases; CRM records; Project histories; QA and process documentation; Business feedback on AI outputs.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
micro1 operational data partnerships ↗Records mentioned: CRM and sales histories; Finance workflows; Support and project records; Chat, email and meeting context; Documents and warehouse records; Private codebases.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Miro Advisory operating data program ↗Records mentioned: Chat and messaging histories; Email and calendar records; Documents and file metadata; CRM records; HR and ERP records; Support-system histories.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Nyne data partnerships ↗Records mentioned: Chat and email; Cloud documents; CRM histories; Support tickets; Design files and call recordings; Accounting and ERP exports.
Polyshares describes this as its typical deal size, with no seller commission. Its stated payment term is net 30–60 after approval, sharing and anonymization.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Polyshares operational data licensing ↗Records mentioned: Code and commits; Internal documents; Decision threads; Financial and CRM records; Support histories; Product logs and sales conversations.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Replay company-data licensing program ↗Records mentioned: Data warehouse records and schemas; Chat histories; Email and calendar records; Documents and metadata; Tickets and knowledge bases; CRM, HR, ERP and support records.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Scale AI data partnerships ↗Records mentioned: Email; Workplace chat; Project trackers; Documents and wikis; CRM records; Code and linked operational history.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Scrimdata company-data partner program ↗Records mentioned: Internal email and chat; Support conversations; ERP, CRM and ticket records; Documents and spreadsheets; Orders and invoices; Fulfillment and supplier histories.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Sell My Business Data offer process ↗Records mentioned: Proprietary source code; Repository and testing history; Technical documentation; Workspace communications; Documents and designs; Project tickets and workflows.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
SimpleClosure AssetHub ↗Records mentioned: Internal communications; Product specifications; Code repositories; Engineering workflows; Customer interactions; Decision and iteration history.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Sunset on purchasing startup data during wind-down ↗Records mentioned: Team conversations; Email threads and attachments; Customer support histories; Business-system records; Company documents and files; Operational decisions and workflows.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Telegraph Lab business-data partnerships ↗Records mentioned: Chat and email histories; Documents and metadata; Project tickets and wikis; CRM and support records; Finance and business-platform records; Code repositories and warehouses.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Troveo business-data licensing ↗Records mentioned: Private codebases; Pull requests; Jira tickets; Product requirements; Architecture documents; Support threads.
Before sending a sample, identify the contracting entity, permitted evaluation use, actual recipients, security process and acceptance conditions. Establish whether the programme acquires a licence, lists supply or introduces another counterparty.
Turing Project Lazarus program ↗Turing official Lazarus code-and-artifact announcement ↗