DatavendorBeta
Sign InSign Up

What buyers use this for

How AI teams source training data, evaluation supply, and custom data work through listings, samples, and briefs.

Off-the-shelf supply

Teams that need ready-made data assets start in Browse listings. The catalog is dense and scannable — type, domain tags, and headline pricing on each row; opening a row shows delivery and asset detail on the full listing record.

Common purchases:

  • Evaluation environments and tasksets for benchmarking models and agents
  • Codebases and zip bundles for training or fine-tuning on real software artifacts
  • Compound listings when a buyer needs multiple deliverable kinds in one transaction

Buyers can save listings to an org-wide shortlist while evaluating options.

Try before you commit

Samples let buyers purchase a small, platform-chosen slice of fungible supply — tasks and environments — before buying the full listing. Sampling is eligibility-gated: the listing needs multiple units of a sampleable kind and a positive per-unit price. Repos and zip bundles are not sampleable.

Use samples to validate format, runtime compatibility, and task quality against your stack before a full buy now purchase.

Custom work through briefs

When off-the-shelf supply is not enough, buyers post a brief: a structured request describing the custom data work they need. Briefs move through Draft → Open → Closed. While open, they are either public (visible in the vendor Project briefs catalog) or invite-only.

Vendors respond by applying — each application is an offer, not a lightweight interest form. When a buyer accepts an offer, a project begins. One open brief can spawn multiple parallel projects if the buyer accepts several applicants.

Who plays which role

Buyers

Organizations that purchase listings or commission custom work. Buyer workflows include browsing and saving listings, sampling and checkout, posting and managing briefs, and tracking projects commissioned from accepted offers.

Vendors

Organizations that list existing assets or respond to briefs. Two commercial paths:

  1. Listing (supply-first) — publish formal assets to the catalog
  2. Brief (demand-first) — apply to buyer requests with tailored offers

Vendors can also submit data proposals to signal inventory they could deliver without a full listing, and run asset estimations on supply they already hold.

Related pages

  • Browse listings — discover supply
  • Buy or sample — purchase or try before you commit
  • Post a brief — describe custom work your team needs

For vendors

  • Publish a listing
  • Submit a data proposal
  • Respond to opportunities

For buyers

  • Browse listings
  • Buy or sample
  • Post an opportunity

Marketplace

  • What you can sell
  • Buyer use cases
  • What are opportunities

Tools

  • Estimate your assets
  • Value your codebase

Help & support

  • Help
  • Contact
  • Support

Legal

  • Privacy Policy
  • Terms of Service
  • Trust Center

Social

  • HUD
  • GitHub
  • X
  • LinkedIn
DatavendorbyHUD