Seller Guides
CAD And Engineering Archives For AI Training
By Basic Trace | Published | Sources checked
Engineering groups keep some of the most detailed records a company has: drawings, models, specifications, test logs and the code behind them. Buyers of company records for AI training describe their interests in broad terms, and engineering files are not always named. This article reads the current public pages of Mode, Mercor and micro1, as of November 18, 2026, to show what each says about engineering material, and sets out the ownership and format questions a seller should resolve first. It is general information about published pages. It does not say that any buyer will accept design files or pay any amount.
What The Buyers Actually Publish
Engineering archives are the least clearly addressed category among the three buyer programs reviewed here, so it helps to separate what is stated from what is only implied. As of November 18, 2026, Mode's home page lists AutoCAD and Figma among "the sources we buy", alongside Gmail, Slack, Jira, Confluence, Salesforce and others, and says the systems and date ranges are agreed before any export (Mode, checked November 18, 2026).
Mercor's page lists Manufacturing as a target industry and gives "work orders, QA logs, spec sheets" as examples. Its supported-tool list shows GitHub with "repositories, commits, PRs, and issues", and it says companies can choose from 100+ supported tools. The visible page does not name a CAD or product lifecycle tool in the excerpts we reviewed (Mercor, checked November 18, 2026).
micro1's data page names "Software & engineering" and describes it as source code documentation, engineering workflows, bug tracking, product planning and technical knowledge bases. It does not mention CAD or design files, and its eligibility FAQ describes SOPs, process documentation, project histories and similar business artifacts (micro1, checked November 18, 2026).
The honest summary is that one program names a CAD system as a source, one names manufacturing paperwork and code repositories, and one describes engineering process content. None of the pages states a price for drawings or models, and none says that a given file format will be accepted.
What Counts As An Engineering Archive
For a seller, the practical question is which parts of an engineering group's output look like the records these pages describe. Using only the categories the buyers list, the likely candidates are:
- Specification sheets, work orders and quality assurance logs, which Mercor names for manufacturing.
- Code repositories with commit history, pull requests and issue trackers, which Mercor lists for GitHub and micro1 describes as engineering workflows and bug tracking.
- Technical documentation, wikis and product planning records, which micro1 and Mode's Confluence and Jira listings cover.
- Design and drawing files held in a system such as AutoCAD or Figma, which only Mode names.
- Email and chat between engineers and customers about requirements, changes and approvals.
Why Drawings And Models Are Harder Than Email
A design file is not like an email archive. A drawing or model often embodies a client's specification, a supplier's part, or a licensed component library, so the company that holds the file may not hold the right to license it. Even where the company owns its own design outright, the file may include a customer's confidential dimensions or a third party's standard parts.
Format matters as well. Binary design files are not plain text, and a buyer's de-identification step, which Mode and micro1 describe in terms of removing or transforming personal identifiers and sensitive material, is easier to describe for documents and messages than for geometry. The pages do not say how a design file would be filtered. That is a question to ask in writing, not to assume.
Ownership And Restrictions To Check First
Before approaching any buyer, a seller should be able to answer the following for each set of files. Every buyer asks about ownership, and Mode says it reviews ownership and access terms before making an offer. micro1 says companies retain ownership of their underlying data (Mode and micro1, checked November 18, 2026).
- Did the company author the file, or did a client, employer or contractor?
- Does a customer contract, nondisclosure agreement or statement of work restrict reuse or disclosure of the design?
- Does the file embed third-party libraries, licensed parts catalogs or open source components with their own terms?
- Does any of the content raise export control or defense-related restrictions? A lawyer should answer this before any transfer.
- Do former employees or contractors have claims to inventions or work product recorded in the files?
- Can the design software still open and export the files, or does the license depend on an account that has lapsed?
Eligibility Still Applies
A strong archive does not remove the eligibility conditions each program publishes. Mode's page lists minimum employees of 10 for legal, 15 for accounting, finance and medical, and 50 for all other businesses, and says it is for companies in the United States, Canada, the United Kingdom and Australia. micro1's FAQ describes established companies with 30 or more full-time employees, primarily English-language data and a current priority on US companies. micro1 also says there is no fixed minimum number of files, documents or terabytes, and that it evaluates depth, breadth, quality and relevance (checked November 18, 2026). Mercor's page, as reviewed, lists no employee minimum.
A small design studio with a large library of files may therefore fall outside the published conditions of two of the three programs, while a larger firm with a modest archive might not.
A Fictional Example
Consider a fictional 60-person mechanical engineering firm that designs fixtures for industrial customers. It holds twelve years of AutoCAD drawings, a ticketing history, project email and a code repository for its test equipment. Reviewing the archive against the questions above, it finds that about two thirds of the drawings were made for customers under agreements that restrict reuse, that its own test-equipment code and internal documentation are fully owned, and that its email is exportable for the last nine years. The firm decides that the owned code, documentation and exportable email are the realistic starting point, and treats the customer drawings as out of scope unless a customer consents in writing. It asks each buyer, in writing, whether design files are accepted at all, how they would be filtered, and what the owned portion alone would be priced against. The firm may be told that drawings are not wanted. That is a useful answer too.
Questions To Put To A Buyer
Ask these before preparing any design files, and keep the answers with your records.
- Do you accept design and drawing files from my system, and in which formats?
- How are customer names, part numbers and confidential dimensions handled before onward delivery?
- Will you accept only the portion we own, and what would be excluded for third-party content?
- Is a sample reviewed by us before use, and can the engagement be ended and files deleted?
- How is a design file priced against email, documents and code in the same engagement?
- What does the agreement say about resale, retention and deletion?
Next Step
If you hold engineering records and are unsure which parts are saleable, a short call is a reasonable way to organize the ownership questions before you approach any buyer. Basic Trace is a market intermediary and cannot confirm that any buyer will accept design files or pay any amount.
Discuss Your Company's Records
Start with what you own, what you can access and what you want to achieve.
Book a call