A shipped game's code, gameplay with its inputs, and the studio's working history are what AI data buyers ask game studios for.

Indie and mid-size studios, mobile and browser game makers, esports organisations and QA firms anywhere in the world: founders and producers deciding whether code, footage and years of studio work can be licensed.

Mercor's listing for game studios puts a deal at $100,000 to $1,000,000 ("Larger studios with full company data have earned more").

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

3 of 4

kinds of record below that the valuation measures or values

3

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.

  • Game and engine code
    Where it sits, and what the evidence shows
    Unity, Unreal or Godot projects with their commit history in GitHub or Perforce.
    How the valuation reads it
    Measured from your code history exportCounted with code with its historyValue a codebasepriced on its own, per repository
  • Gameplay with inputs
    Where it sits, and what the evidence shows
    Recordings synced with keyboard, mouse or controller input, and full-length footage of the studio's own games.
    How the valuation reads it
    Describe it in your offer
  • The studio's working history
    Where it sits, and what the evidence shows
    Slack or Discord, Jira and shared drives: how the team built and shipped.
    How the valuation reads it
    Measured from your chat exportCounted with conversations
  • Player and playtest data
    Where it sits, and what the evidence shows
    Analytics, playtest telemetry and support tickets.
    How the valuation reads it
    Measured from your tickets exportCounted with tickets and projects

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 company records, game code and gameplay footage behind the games you've shipped.”
    Mercor, its listing "Game Studio"Its own page, 27 Oct 2026
  • “At least one shipped title that earns revenue. A team of 10+ people working together, not mainly short-term contractors. Company records the studio owns: chat, tickets, code and shared drives”
    Mercor, what the listing asks forIts own page, 27 Oct 2026
  • “Game and engine code with commit history. Gameplay video synced with keyboard, mouse or controller input. Full-length gameplay videos and trailers of your own games. Player analytics, playtest telemetry and support tickets. Design documents and 3D assets”
    Mercor, what it would also likeIts own page, 27 Oct 2026

What raises the value

  • Gameplay recorded with the player's inputs.
  • Code with its full commit history, not a snapshot.
  • A team that worked together for years, not mainly short-term contractors.
  • History the listing measures in its own words: "At least one shipped title that earns revenue".

What lowers the value

  • What the listing rules out: "Footage of other studios' games", "Asset-store or template code", "Crypto and play-to-earn token projects".
  • Asset-store or template code.
  • Footage of other studios' games.

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
  • Code and assets made with engines or middleware stay under their licences: third-party plugins and store assets come out of the lot.
  • Player data is personal data: analytics and tickets go only de-identified, and players who are children are a regime of their own.
  • A publisher deal may own the game, its code or its footage: read it before counting a title in.

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.

Every lot on offer

204

lots on offer like yours

4.3 years

of history in the middle of them

14 of 65

say the rights are settled

What holders like you ask

What is a game studio's data worth to an AI buyer?
Mercor's listing for game studios puts a deal at $100,000 to $1,000,000 ("Larger studios with full company data have earned more"). It asks for 10–500 employees (Anywhere; international studios welcome). 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 "At least one shipped title that earns revenue", "A team of 10+ people working together, not mainly short-term contractors", "Company records the studio owns: chat, tickets, code and shared drives". It would also like "Game and engine code with commit history", "Gameplay video synced with keyboard, mouse or controller input", "Full-length gameplay videos and trailers of your own games", "Player analytics, playtest telemetry and support tickets", "Design documents and 3D assets". It rules out "Footage of other studios' games", "Asset-store or template code", "Crypto and play-to-earn token projects".
What will a buyer ask us first?
Mercor's listing names its first questions: "How many titles have you shipped, and do they earn revenue?", "How many people work at the studio, and which tools does the team use?", "Do you own the game and engine code outright?", "Do you record gameplay or playtests with input logs?". 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.

Value your company's recordsCheck an offer you have