Every build with its recipe and its result, failures included, is what AI data buyers ask chip and materials makers for.

Fabs and foundries, device makers, fabless designers, equipment makers and materials or battery labs, operating or wound down: founders and engineering leads deciding whether run records can be licensed.

Mercor's listing for semiconductor and materials companies puts a deal at $100,000 to $750,000 ("Depends on run count and how well runs link to results").

AIData.Broker represents you in selling it: we value your data against public prices, describe it without your name to every buyer whose published rules it meets, at the same time, and help you negotiate the terms, for holders based in the United States, the United Kingdom and Canada. Our fee is 12% of the first $250,000 a sale pays you, and nothing if no sale closes.

1

buyers quoted below on what they want from companies like yours

2 of 4

kinds of record below that the valuation measures or values

2

rights questions to settle before a buyer sees a record

What companies like yours hold

What you typically have, where it sits, and whether the valuation can measure or value it. Buyers price what exists together, over how many years, and how well it links.

  • Run and build records
    Where it sits, and what the evidence shows
    Each build's recipe or process settings with its measured result, in the MES, SPC and yield systems or a LIMS.
    How the valuation reads it
    Describe it in your offer
  • Lab notebooks
    Where it sits, and what the evidence shows
    Electronic notebooks with the reasons builds failed.
    How the valuation reads it
    Measured from your documents exportCounted with documents and knowledge
  • Equipment and metrology logs
    Where it sits, and what the evidence shows
    Tool data and measurements, often in OSIsoft PI.
    How the valuation reads it
    Describe it in your offer
  • Designs with their test results
    Where it sits, and what the evidence shows
    Chip or device designs (Cadence, Synopsys) with verification and test outcomes.
    How the valuation reads it
    Measured from your code history exportCounted with code with its historyValue a codebasepriced on its own, per repository

What buyers say they want from companies like you

In their own words, from their own pages or from reporting on what they bought. Each opens its source.

  • “License the run records that tie each recipe to a measured result.”
    Mercor, its listing "Semiconductor & Materials Company"Its own page, 27 Oct 2026
  • “Run or build records the company owns, with recipe or process settings linked to measured performance. 1,000+ runs, builds, wafers or experiments. Every build kept, failed ones included, with dates. Data that hasn't been published”
    Mercor, what the listing asks forIts own page, 27 Oct 2026
  • “Lab notebooks with notes on why builds failed. The same recipe built again on different days. Measurements under more than one condition. Yield, metrology and equipment logs. Chip or device designs with their verification and test results”
    Mercor, what it would also likeIts own page, 27 Oct 2026

What raises the value

  • Failed builds and repeat runs kept, not only the successes.
  • The same recipe built again on different days.
  • Notes that explain why a build failed.
  • History the listing measures in its own words: "Several years of runs".

What lowers the value

  • What the listing rules out: "Data owned by a customer or foundry partner", "Published papers and datasheets only", "Licensed third-party IP".
  • Results already published in papers or datasheets.
  • Runs with no link from settings to outcome.

A line that quotes a buyer names it. The others are our checklist, drawn from the factors buyers state in general: no buyer publishes how much each one moves a price. How often each factor matters across 156 kinds of data.

The rights to settle first

These stop a sale more often than price does. Each can be settled before any buyer sees a record.

The full rights checklist
  • Data made for a customer or with a foundry partner is often theirs under the contract: only what the company owns can be licensed.
  • Export controls apply to some semiconductor technology: a sale to a foreign buyer may need a licence.

What is already on offer from companies like you

Read this morning from the brokers' and marketplaces' own catalogues. A buyer compares your records with these; settled rights, more years and more linked systems are what set one apart.

29

lots on offer like yours

9 years

of history in the middle of them

8 of 24

say the rights are settled

What holders like you ask

What is a semiconductor or materials company's data worth to an AI buyer?
Mercor's listing for semiconductor and materials companies puts a deal at $100,000 to $750,000 ("Depends on run count and how well runs link to results"). It asks for 10–2,000 employees (Anywhere). What moves an offer within the range is what the listing names: how complete the records are, how far back they go and whether you can license them.
What exactly does the buyer ask for?
Mercor's listing asks for "Run or build records the company owns, with recipe or process settings linked to measured performance", "1,000+ runs, builds, wafers or experiments", "Every build kept, failed ones included, with dates", "Data that hasn't been published". It would also like "Lab notebooks with notes on why builds failed", "The same recipe built again on different days", "Measurements under more than one condition", "Yield, metrology and equipment logs", "Chip or device designs with their verification and test results". It rules out "Data owned by a customer or foundry partner", "Published papers and datasheets only", "Licensed third-party IP".
What will a buyer ask us first?
Mercor's listing names its first questions: "What run or lab records do you keep, and in which systems?", "Roughly how many runs or builds, over how many years?", "Do you keep failed builds and repeat runs?", "Do you own the data, and has any of it been published?". Have the answers before you start.
How do we sell through you?
Start with the valuation. It reads what you hold against public prices and against the rules each buyer publishes; then either we run the sale for you, describing your records without your name to every buyer whose rules they meet, or, where a buyer's own programme fits you better, we introduce you to it, free for you. The holder pays us a fee fixed in the mandate, and only if a sale closes. In a sale we run no buyer pays us, so our fee depends on what you are paid, not on which buyer pays it. A buyer pays us only if you choose to apply to it through its own referral programme, and you see that amount in writing before you choose.

In this topic

What sells

  1. Start hereWhich data do AI labs want, and who holds it?Each kind of data the market prices, the businesses that hold it, what labs are asking for now and what they turn away.
  2. GuideWhat Are RL Environments? Who Builds, Buys and Prices ThemAn RL environment is a sandbox where an AI agent attempts tasks with tools and a verifier scores each try. Who builds them, who buys them and what they cost.
  3. GuideHow to Sell Your Videos for AI Training: Prices and BuyersAI companies pay to license your videos for training, by the hour or the minute. What each buyer pays, which footage sells, and the rights every frame needs.
  4. GuideSelling audio and speech recordings for AI trainingWhat AI companies pay for call recordings, podcasts, radio, meeting audio and voice data, why archive audio sells cheapest, and the recording-consent law state by state.
  5. GuideSelling photos and image archives for AI trainingWho buys photos for AI training, what stock agencies pay contributors (shares and bonuses, not prices), what image archives sell for, consent and releases agency by agency, and how to prepare a library for a sale.
  6. GuideSelling your company's Slack data for AI training: what the export allows and who buys itYes, a company can license its Slack history to AI buyers. What Slack's export and API terms allow on each plan, whose messages are inside, what buyers pay and the steps.
  7. GuideSelling company documents and shared drives for AI trainingYes, a company can license its documents, wikis and shared drives to AI buyers. Which documents they pay for, what Google Workspace, Microsoft 365, Confluence and Notion let you export, who owns the files, and the steps.
  8. GuideSelling customer support tickets and chats for AI trainingOften yes, after three checks: your customer contracts and privacy notice, your help desk's export terms, and removing personal data. What buyers want in a ticket, what records with tickets fetch, and the steps.
  9. GuideSelling a company's email archive for AI training: exports, consent and priceYes, a company can license its own email to AI buyers. How Google Workspace and Microsoft 365 let you export a whole organisation's mail, the deadlines when a subscription lapses, the law on staff and customer messages, and what buyers pay.
  10. GuideSelling CRM data for AI training: Salesforce and HubSpot records, consent and priceA company can license its CRM history to AI buyers, but CRM records are customer data first. What buyers value in Salesforce and HubSpot, how each lets you export, why the contact list usually stays out, and what CRM history fetches.
  11. GuideSelling meeting recordings and transcripts for AI trainingCan a company license its Zoom, Google Meet or Teams recordings and notetaker transcripts to AI buyers? Recording consent state by state, what Zoom's terms allow, what meeting audio and transcripts fetch, and the steps.
  12. GuideSelling accounting and finance records for AI training: QuickBooks, Xero and NetSuiteA company can license its accounting history to AI buyers, but finance records carry customers', suppliers' and lenders' confidential terms and staff payroll. What buyers value in QuickBooks, Xero and NetSuite books, how each lets you export, what has to come out, and what finance records fetch.
  13. GuideSelling Jira and Linear issue history for AI trainingYes, a company can license its Jira or Linear issue history to AI buyers. It is valued when each issue links to the code that closed it. What each export keeps, what buyers ask for, and what it fetches.
  14. GuideSelling design files and product history for AI training: Figma and beyondYes, a company can license its Figma files and design history to AI buyers. What buyers value, what Figma lets you export, client work, fonts and other assets that are not yours, who owns the designs, and the steps.
  15. GuideSelling IT service desk records for AI training: ServiceNow tickets, runbooks and incidentsOften yes. IT tickets, incidents and runbooks teach agents to resolve real problems, once credentials, hostnames and people are removed. What ServiceNow and Jira Service Management let you export, what buyers ask for, and what the records fetch.
  16. GuideSelling Books to AI Companies: Prices, Deals and Who Gets PaidAI companies license books by the title, mostly from publishers' backlists. What deals paid per book, how much reaches the author, and how to sell a catalogue.
  17. GuideSelling Game Code and Game Data to AI CompaniesAI companies license game studios' code with its history and gameplay recorded with the player's inputs. Who buys, what studios are offered, and what you may not sell.
  18. PageWhere data comes fromWho holds each kind of data, how much exists and how it reaches buyers.
  19. RegisterCompanies closingCompanies closing, sold or gone dark, and the records they leave.

See what you hold, measured on your own computer. Only the counts leave it.