Glossary

Terms are alphabetical. Headings double as anchors, so /overview/glossary#listing links straight to a definition.

​

Archive

Retiring a listing from the marketplace and your workspace. Archiving withdraws open bids and cancels pending purchases; buyers who already paid keep access. Restore listing brings it back. There is no delete. See also: Hide from catalog, Listing lifecycle.

​

Asset

One unit of supply attached to a listing: a HUD taskset, an environment, a repository, or a Raw data ZIP. A single listing can bundle several asset kinds, and each kind has its own pricing unit. Distinct from an inventory asset, which exists on your team before it is listed. See also: Inventory asset, Taskset, Environment, Pricing units.

​

Asset stage

Where an inventory asset stands, set by DataVendor from what the asset holds: Incomplete (details missing), Proposed (details filled in, no data linked), or Complete (details filled in and data linked). See also: Inventory asset.

​

Bid

A buyer’s own-price offer on a published listing. The vendor accepts or rejects without ever seeing who bid, and an accepted bid still needs checkout at the bid amount before anything is delivered. Bids do not expire. The API calls bids offers: /v2/listings/browse/{id}/offers, list_my_offers. Distinct from an offer on a legacy project opportunity. See also: Purchase, Offer.

​

Browse gate

The catalog rule for vendor-only teams: until you have 2 live published listings of your own, you see only the first page of the unfiltered catalog. Searching, filtering, sorting, and further pages unlock at that point, and the browse page shows your progress. Listing records always open from a link, and buyer teams are exempt. See also: Listing, Visibility.

​

Connector

A link between your DataVendor user and a service your supply lives on: GitHub, GitLab, or Bitbucket for repositories, plus the built-in HUD connector. Connectors belong to the person, not the organization. See Connect your accounts.

​

Credits

HUD platform currency, used for platform usage such as credit-priced recommended environment checks. Vendors convert available earnings to credits 1:1 with no fee; the conversion is irreversible. Marketplace purchases are paid by card or invoice, not credits. See also: Wallet, Withdrawal, QC check.

​

DV quality certified

The verified badge: DataVendor’s approval that a listing meets its marketplace quality standards. A listing earns it when every quality check with a verdict passes on its latest run, none skipped, including every recommended environment check that applies to its assets. Buyers see it next to the listing title and can filter the catalog to Verified only. The badge belongs to the listing, not the vendor account; editing the listing or refreshing its assets removes it until checks pass again. See also: QC check, Skip review, Freshness.

​

Entitlement

The access a buyer team holds after a paid purchase. An entitlement keeps the purchased listing detail and its deliverables available even if the vendor later edits, hides, or archives the listing. The purchase is the transaction; the entitlement is what it grants. See also: Purchase.

​

Environment

A runnable software environment on HUD that tasks execute against. Environments are sold with the HUD tasksets that run on them, never on their own, and share one Per Environment rate on a listing. See also: Taskset, Task, Sample.

​

Freshness

Whether a linked HUD environment or taskset still matches its live source. Vendors can probe a single asset against its source, or refresh every snapshot; a refresh returns the listing to Draft and voids certification. Repositories do not track freshness; the archive pins the commit it captured. See also: Source fingerprint, DV quality certified.

​

Harbor tasks

Tasks in the Harbor benchmark format, delivered as a ZIP. A retired asset kind: listings that already carry Harbor tasks keep selling, but new listings cannot add them. To sell them, import them to HUD and add them as Tasks; see Add assets. See also: Asset, Taskset.

​

Hide from catalog

Taking a live listing out of Browse marketplace without archiving it. Available only before anyone has bought or sampled the listing; Go live publishes it again. See also: Archive, Visibility.

​

Inventory asset

Something your team could sell, kept in Inventory independently of any listing: a codebase, a Raw data ZIP, or a task imported from HUD, with its own description, domain, and asking price. An asset can be registered before its data is linked; until then it never appears in the catalog. One asset can sit in several listings. Codebases and Raw data can be listed from Inventory; other kinds cannot yet. See also: Asset stage, Asset, Listing.

​

Listing

A formal marketplace offer of existing assets (HUD tasksets with their environments, repositories, or Raw data ZIPs) with pricing and delivery terms. Buyers purchase the whole listing or a sample, never individual assets. See also: Asset, Listing lifecycle, Visibility, Sample.

​

Listing lifecycle

Where a listing sits in the vendor workflow: Draft (composing) → Checking (automated quality checks run after submit) → Ready (cleared to go live) → Active (published in the catalog), with Needs attention when a check flags something to fix. Archived listings are retired and can be restored; Rejected listings were turned down by DataVendor. Editing a submitted listing returns it to Draft. Lifecycle is separate from visibility. See also: Visibility, QC check, Archive.

​

NDA

The Mutual NDA (mutual non-disclosure agreement) between you and Human Union Data, Inc., the company behind DataVendor. You accept it before the workspace opens. Acceptance belongs to you, not your organization, and a newly published version asks you to accept again. Listing submit needs no separate signature. Distinct from the Platform Access Agreement that unlocks Tier 2. Read it at datavendor.ai/legal/mutual-nondisclosure-agreement. See also: PAA, Tiers.

​

Offer

A vendor’s priced application to a legacy project opportunity. Applying is retired; existing offers are read-only history under Projects. Distinct from a bid, which is a buyer’s own-price offer on a listing, even though the API names bids offers too. See also: Project, Bid.

​

Opportunity

A buyer’s request for listings that meet stated requirements, with a submission deadline. The buyer can post it publicly or anonymously. DataVendor reviews each request and sets which vendors see it. Tier 2 vendors respond by submitting listings until the deadline, or until the buyer closes the request. See also: Tiers, Listing, Project.

​

PAA

The Platform Access Agreement. Signing it grants Tier 2 immediately and unlocks opportunities for your organization. It appears under Settings → Agreements as Tier upgrade agreement. See also: NDA, Tiers, Opportunity.

​

Payout

Money leaving DataVendor for a vendor’s bank. After a withdrawal is approved, DataVendor releases the transfer to the vendor’s connected Stripe balance, and Stripe’s payout schedule owns bank delivery from there. See also: Withdrawal, Credits.

​

Platform fee

DataVendor’s 20% share of vendor earnings, assessed only when earnings are withdrawn; converting earnings to credits is fee-free. Buyers separately pay a small transaction fee, shown at checkout. See also: Withdrawal, Credits.

​

Price guidance

DataVendor’s advisory per-unit price band shown while pricing a listing, blended from the listing’s domain tags. Guidance never blocks saving or submitting. See also: Pricing units, Listing.

​

Pricing units

How each asset kind is priced: one Per Task rate shared across attached tasksets, one Per Environment rate shared across their environments, a Per repository price for each repository, and a Per Bundle price for each Raw data ZIP. A Sample price sets what a sample costs. The buy-now total is the sum. See also: Asset, Price guidance, Sample.

​

Project

A historical engagement from a legacy project opportunity. Project details, task status, and attachments are read-only under Projects for the buyer and vendor involved. See also: Offer, Opportunity.

​

Purchase

A buyer transaction on a listing: Buy now, an accepted bid checkout, a sample, or an invoice-paid order. Paid purchases grant entitlements and appear under Purchases. See also: Entitlement, Bid, Sample.

​

QC check

An automated quality check run against a listing’s assets after submission. The report groups checks in three steps: Required to publish (mandatory checks, free, gate publishing), Verified badge (every other check, including the credit-priced recommended environment checks, which together decide DV quality certification), and Insights (A to D measurements with no verdict). See also: DV quality certified, Skip review, Credits.

​

Sample

A small purchase from a listing that DataVendor chooses: one environment drawn at random plus one task that runs on it, at the listing’s sample price. Only listings with HUD tasksets that hold at least two runnable tasks can offer one, never repositories or Raw data. One sample per buyer team per listing. See also: Task, Environment, Entitlement.

​

Skip review

A vendor action that marks a run’s unresolved optional checks skipped and moves the listing to Ready without DV quality certification. It is available only once every mandatory check has passed. See also: QC check, DV quality certified.

​

Source fingerprint

The snapshot identity of a listing asset: the archived commit for repositories, a content hash over live tasks for tasksets, and the latest build for environments. Fingerprints re-baseline when assets change, on submission, and on explicit refresh. See also: Freshness, Asset.

​

Task

A concrete runnable instance created from a task template in the context of a specific environment. Samples deliver task instances, not bare templates. Vendors can also import tasks into Inventory, one asset per task. See also: Taskset, Environment, Sample.

​

Taskset

A set of task templates authored against one or more environments. Tasksets share one Per Task rate across all tasksets attached to a listing, counted over their templates. See also: Task, Environment, Pricing units.

​

Team admin

A member with the admin role in an organization. Only team admins move money or make deals: buying, bidding, invoicing, accepting or rejecting bids, converting earnings, and withdrawing. They also change members’ roles. See also: Wallet, Bid.

​

Tiers

Vendor access levels. Tier 1, granted when vendor organization setup finishes, unlocks listings (accept the Mutual NDA to open the workspace). Tier 2, granted on signing the Platform Access Agreement, unlocks opportunities. Tier 3 is invite-only and adds opportunities that require it. See also: NDA, PAA, Opportunity.

​

Visibility

Who can discover an Active listing, independent of its lifecycle stage: a public listing enters the browse catalog when published, while a private listing is live only for the buyer teams of the opportunities it is submitted to. See also: Listing lifecycle, Browse gate.

​

Waitlist

The queue buyer organizations join before DataVendor grants buyer access. A waitlisted organization shows as Waitlist · buyer until it is approved. See Become a buyer.

​

Wallet

Your team’s balances on DataVendor. For vendors: credits plus earnings, with earnings split into total, pending, and available. Sales credit the wallet as pending earnings that settle 14 days after payment before they can be converted or withdrawn. For buyers: HUD credits and saved payment methods. See also: Credits, Payout, Withdrawal.

​

Withdrawal

A vendor request to pay out available earnings to a bank. Withdrawals are quoted (gross, platform fee, estimated Stripe transfer fee), require Stripe payout setup, and pass DataVendor review before the transfer is released. See also: Payout, Platform fee, Wallet.