Skip to main content

Menu

Train on private data

Email the sapien1 team about the data or tasks you need. We’ll discuss suitable samples, permitted uses and delivery.

Example review

The right training data can be hard to find. Start with the task your model needs to learn.

Browse codebases, tasks, and company data

Explore examples of materials a buyer can request. Availability depends on the supplier and licensing rights.

Underwriting engine

Java · 920k LOC

Example

Payroll platform

TypeScript · 1.2M LOC

Example

Freight routing

Go · 540k LOC

Example

Clinic scheduling

C# · 680k LOC

Example

Trading risk service

Rust · 310k LOC

Example

Storefront monolith

Ruby · 450k LOC

Example

Claims adjudication

Kotlin · 760k LOC

Example

Factory execution system

Python · 390k LOC

Example

Inventory planner

Java · 410k LOC

Example

Telehealth backend

Go · 280k LOC

Example

Ad bidding engine

C++ · 650k LOC

Example

Insurance quoting

TypeScript · 520k LOC

Example

Logistics dispatch

Python · 340k LOC

Example

Banking core

Java · 1.4M LOC

Example

Booking platform

PHP · 610k LOC

Example

Grid telemetry

Rust · 220k LOC

Example

Bring a brief, or start with a sample

Tell us what your model needs. A sample can show whether the available material fits your task.

How to describe a request

Sample preview

  • Payroll SWE tasks

    2,400 tasks

    Example
  • Payroll platform

    TypeScript · 1.2M LOC

    Example
  • Payroll admin

    480 tasks

    Example
  • Finance ledger exports

    640M rows

    Example

Buyer brief

Example

Can we evaluate an agent on payroll corrections?

Task
Correct a payroll entry
Source
Payroll records and change history
Evidence
Expected result and scoring rule

Review the quality evidence

Look at permissions, sensitive information, coverage and known limitations before agreeing on a delivery.

Sample preview · Support tickets

Payroll engineering tasks

Example review
  1. Source and permissions
  2. Personal information
  3. Repository history
  4. Task instructions
  5. Reference answers
  6. Evaluation criteria

Review notes

  1. Confirm the source and permitted use.
  2. Run the tasks on a sample.
  3. Record missing files and ambiguous cases.
Example review · Support tickets
Request number
R-07
Task
Return a damaged item
Policy version
Not recorded
Outcome
Refund issued

In this fictional sample, 10 of 12 cases link to the applicable policy and 11 have a recorded outcome. Ask for the missing evidence before accepting the collection.

Review notes

Agree on the scope and terms

Set out what the delivery includes, the permitted uses and how you will check it.

Payroll task collection

Example scope

Proposed sample

A small set of payroll corrections with reference answers.

Can’t find it? Send a request

Describe the data, the intended use and any constraints. sapien1 can discuss sourcing options with you.

Request for customer support data

Requested materialSupport calls and transcripts

Matching examples0

  • Ticket history export

    Support tickets

    Example
  • Customer support calls

    Call recordings

    Example
  • Calls with transcripts

    Audio and text

    Example
  • Support desk archive

    31M records

    Example
  • Help desk triage tasks

    Task environments

    Example
  • Team chat archive

    40M messages

    Example

How buying works

  1. 1. Share a brief

    Describe the source, format and task you have in mind.

  2. 2. Evaluate

    Review a sample and the evidence for your use case.

  3. 3. Agree on delivery

    Confirm the license, deliverables and acceptance criteria.

Find data for your next model

Talk to sapien1 about your training or evaluation project.

Language: English