Learn from real work
You need operational records that preserve context across conversations, tasks, documents, code and outcomes.
Tell us the task your model needs to perform. We find datasets with the right records, check coverage with their owners and help you test available samples before you license the data.
Start with one research task and what a sample would have to show.

Real-world collections for teams building and evaluating AI. Explore where your data fits.
A whole-company archive or selected systems. Connected records can follow a customer request through decisions, work and its outcome.
Start with your sector, team size, systems and years of history. The records can still be in the tools you use today.

Healthcare operations, medical imaging and clinical collections, subject to a review of rights, permissions and privacy.
Useful details: care setting, record types, coverage and de-identification status. Start with descriptions, not patient information.

Engineering collections with the geometry, drawings and context behind each design.
Useful details: file counts, formats, engineering discipline and design history.

Human demonstrations, robot recordings and sensor data from real environments.
Useful details: recorded hours, tasks, camera setup and capture location.

A game collection can pair its source code and assets with a build or gameplay recording. When development history is available, researchers can trace a mechanic back to the commits and tasks that shaped it.
Useful details: engine and version, supported platforms, build instructions and which rights the owner can license.

Research collections across earth, physical, mathematical, life and engineering sciences.
Useful details: research domain, collection method and validation.

Recordings paired with the transcripts, labels and context that make them useful.
Useful details: duration, languages, annotation coverage and consent status.

Interactive environments, tasks and demonstrations for training and evaluation.
Useful details: task scope, interfaces, dependencies and evaluation method.

In this example, the job ID connects an estimate, a drawing and an invoice. A researcher can test whether a model follows the right revision through all three records.
Task, category, required systems, geography, formats, volume, coverage and acceptance criteria.
Which criteria are essential and which are preferences.
Contents by system, available amounts and dates, record relationships, provenance and known gaps.
Whether the material is relevant enough to inspect.
Available sample files, supporting context and requests for missing records or complementary information.
Whether the data passes your own technical review.
Permitted use, authority, exclusivity where available, price, delivery formats and conditions to resolve with the owner.
What can be licensed and on which terms.
Coverage varies by dataset. Unknown, estimated and supplier-reported information must remain distinguishable from verified facts. Suitability for an RL environment or evaluation task requires your technical review.
| Source | Record | What connects it |
|---|---|---|
| Estimator | Estimate EST-42 | Job J-042 · accepted revision 2 |
| Project folder | Drawing D-42 | Job J-042 · revision 2 built |
| Accounting | Invoice INV-42 | Job J-042 · references EST-42 |
A reviewer can follow the accepted design into the drawing and invoice. A shared job ID makes the join testable.
You need operational records that preserve context across conversations, tasks, documents, code and outcomes.
Your research calls for particular formats, modalities or metadata in healthcare, CAD, robotics, games or another specialist field.
You need to inspect the source material, linkage and completeness before deciding whether it can support your training or evaluation work.

If your model has to reconcile an invoice, it needs the accepted estimate and the job it belongs to. We check for those links and ask the owner for missing records.
Communications, documents and operational history across company systems, with the links between them where available.
Healthcare, engineering and CAD, robotics, games and more. Search for the actual contents, formats and history your work needs.
Review available samples, inspect the structure and identify gaps. Request the missing records or details in your company workspace.
Define the source, rights and delivery requirements. Agree the scope of a licence with the data owner before proceeding.
Company records, work history and connected systems.
License first-person recordings of physical work or brief us on a robotics collection.
Start with the owner assessment to tell us what your business holds.
Give us a specific brief. Your team can browse and save datasets in a shared workspace, or use the API and MCP from your own agent.
Prepare your briefUse a structured buyer request to separate essential criteria from preferences.
Compare matching inventory, download available samples and collect any missing information.
Work through scope, rights, price and delivery with the data owner. The terms follow the actual dataset.
Dataset coverage, intended use, exclusivity, preparation and delivery affect commercial terms. We work through those details with the owner. A catalogue entry or sample does not by itself grant training rights or promise a model-performance improvement.
Available samples can be downloaded through the buyer workspace when access conditions permit. If a sample is missing, your team can request it. Sample availability and any restrictions depend on the dataset.
Yes. Define the systems, formats, coverage, volumes, linkage, metadata and acceptance criteria that matter. Separate hard requirements from preferences so a relevant category is not mistaken for a complete match.
Record the specific gap against the dataset. Maryah can collect the additional detail or files from the owner and add them to the same record, rather than create a separate version for each buyer.
Not necessarily. Some datasets can provide material for tasks and environments, but raw records are not the same as an executable environment with tools and a verifier. Review what each package actually includes.
The buyer workspace supports API and MCP access using the company's access permissions. Your agent can review available information and work with structured requests; the workspace remains available for manual review.
Catalogue access is controlled through a Maryah password or an authorized buyer workspace. Rights are agreed for the particular dataset and use case; access to a listing does not create a uniform licence across the catalogue.
Send a task, the records it requires and what a sample must show. We’ll review available datasets against those criteria and identify what we need to source from owners.
An existing RFP works too.