What you can sell
Codebases, task sets, evaluation environments, and operational data can all be described for a supplier review.
Supply types
Describe the type of material and the work that produced it. Five common starting points are:
- Evaluation environments — runnable tasks with a starting state, permitted actions, and a way to check the result.
- Task sets — related tasks with instructions, inputs, and expected outcomes.
- Codebases — repositories or snapshots with a known origin and licensing history.
- File bundles — collections of documents, images, audio, or structured records.
- Operational data — records produced by real work, such as support exchanges or event histories.
Include a rough quantity, the period covered, and any restrictions that apply. A description is enough to start a review.
Connectors
Use the collection description to identify where the material lives. You can discuss a transfer method after reviewing the rights and scope.
| Source | Material | First step |
|---|---|---|
| Source control | Codebases | Describe the repository and ownership. |
| Task runtime | Environments and task sets | Describe how a task starts and finishes. |
| File storage | Archived collections | List the formats and approximate size. |
| Business systems | Operational data | Identify the record types and time span. |
Marketplace listings
A listing records what a supplier can deliver. Note whether different parts of a collection have different owners, permissions, or delivery requirements.
Asset kinds on a listing
| Kind | What to describe |
|---|---|
| Environment | Runtime, actions, and how success is measured. |
| Task set | Instructions, inputs, labels, and number of tasks. |
| Repository | Languages, scope, dependency rights, and snapshot date. |
| File bundle | Formats, record count, provenance, and partitions. |
Pricing
Specify the unit behind a price, such as a task, licensed collection, or delivery. Training rights, exclusivity, update frequency, and support can change what the price covers.
Data proposals
A proposal describes material you could supply. It is useful when you know the source and rights but have yet to prepare a delivery.
- Evaluation environments and task sets
- Codebases and raw datasets
- Audio, video, and traces
- Enterprise documents and operational records
Listing vs proposal
| Listing | Data proposal | |
|---|---|---|
| Readiness | Existing, described assets. | Existing or possible supply. |
| What to include | Delivery details, usage rights, and pricing unit. | Description, capacity, source, and expected timing. |
| Next step | Review a sample and terms. | Discuss feasibility and demand. |
Asset estimation
Use the supplier form to describe a collection for pricing review. Include the rights you control and the kind of license you can offer.
Related pages
- What a listing is — Prepare the details of a codebase, task set, environment, or file collection for review by sapien1.
- What a data proposal is — Describe what your organization can supply before preparing a complete delivery.
- Estimate your assets