What you can sell
RL environments, tasksets, codebases, zip bundles, and operational data — as formal marketplace listings or lighter-weight data proposals.
Supply types
Vendors can bring five kinds of supply to market:
- RL environments — runnable agent evaluation environments on managed Harbor or HUD infra, priced per environment
- Tasksets — reusable task templates for benchmarking, priced per task on managed infra
- Codebases — GitHub repositories delivered as self-hosted downloads with redacted file-tree previews
- Zip bundles — archived files of any mix (datasets, documents, media, or other bundled supply), delivered as a self-hosted download with redacted tree previews
- Operational data (coming soon) — CRM exports, SaaS data, SOPs, process docs, and other records that describe how your company runs
Zip bundles are the current file-upload path for bundled supply. Operational data is a distinct category for SaaS and enterprise records; HubSpot and Salesforce connectors for that category are not live yet.
Connectors
Attach supply through connectors or direct file uploads:
Marketplace listings
A listing is a formal marketplace offer: one or more assets with pricing, previews, and delivery details. Buyers browse live listings in the catalog, sample eligible supply, or buy the full bundle.
Listings can be compound — a single offer bundling multiple asset kinds (for example, RL environments plus tasksets plus a repo). Buyers purchase the whole listing or a platform-chosen sample; partial asset purchases are not supported.
Asset kinds on a listing
Each asset carries its own delivery: runtime targets (Harbor or HUD for managed kinds; self-hosted download for repos and zips) and setup instructions.
Pricing
Vendors set per-asset-type pricing — one unit price per kind (per task, per environment, per repo), multiplied by quantity. Buy now checkout runs through Stripe. Samples are available only for fungible kinds (tasks and environments) when the listing has more than one sampleable unit and a positive per-unit price.
Data proposals
A data proposal is lighter-weight supply intent: what your org could deliver on short notice if buyer interest appears, without investing in a finished listing yet. HUD uses proposals for buyer matching and supply analytics.
Proposals never appear in the public catalog. They live under My listings → Proposals and use a broader data proposal asset type taxonomy than formal listings:
- RL environment
- Taskset
- Codebase
- Raw dataset
- Audio
- Video
- Traces
- Enterprise documents (operational data)
If demand materializes, you can publish a listing self-serve — often pre-filled from the proposal.
Listing vs proposal
Asset estimation
Asset estimation is separate from both paths above. It values supply you already have (for example, signals from a GitHub codebase) and can pre-fill the publish-listing flow.
Related pages
- Publish a listing — formal marketplace offer with assets and pricing.
- Submit a data proposal — declare capacity without a finished listing.
- Estimate your assets — get a value range for supply you already hold.