Skip to main content

Menu

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:

  1. Evaluation environments — runnable tasks with a starting state, permitted actions, and a way to check the result.
  2. Task sets — related tasks with instructions, inputs, and expected outcomes.
  3. Codebases — repositories or snapshots with a known origin and licensing history.
  4. File bundles — collections of documents, images, audio, or structured records.
  5. 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.

SourceMaterialFirst step
Source controlCodebasesDescribe the repository and ownership.
Task runtimeEnvironments and task setsDescribe how a task starts and finishes.
File storageArchived collectionsList the formats and approximate size.
Business systemsOperational dataIdentify 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

KindWhat to describe
EnvironmentRuntime, actions, and how success is measured.
Task setInstructions, inputs, labels, and number of tasks.
RepositoryLanguages, scope, dependency rights, and snapshot date.
File bundleFormats, 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

ListingData proposal
ReadinessExisting, described assets.Existing or possible supply.
What to includeDelivery details, usage rights, and pricing unit.Description, capacity, source, and expected timing.
Next stepReview 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

Language: English