> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datavendor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a listing

> Package assets into a listing, price it, and submit it for review.

A **listing** is a formal offer of assets you already hold: HUD tasksets, codebases, or Raw data
ZIPs. Buyers purchase the whole listing or a [sample](/buy/try-a-sample), never individual
assets.

There are two ways to start. If your workspace has [Inventory](/sell/inventory/overview), list
codebases and Raw data straight from it. To list HUD tasksets, or if you have no Inventory, use
**Add listing** in **Listings**.

## From Inventory

<Steps>
  <Step title="Select assets">
    In **Inventory**, select codebases or Raw data with linked data and choose **List for sale**,
    then one listing per asset or one listing for all of them. Assets without linked data are
    skipped, and other asset kinds cannot be listed from Inventory yet. A Raw data asset lists as a ZIP; its
    content tag, when it has one in its extra columns, comes along.
  </Step>

  <Step title="Price and describe">
    Each listing opens as a draft. Set an asking price for each asset, then write the title,
    one-liner, and listing description, and pick its domains. A draft saves with just a title;
    the one-liner and listing description are required before you submit.
  </Step>

  <Step title="Submit">
    Check **I confirm ownership of this supply** and **I confirm this listing meets quality
    terms**, then choose **Submit for review**.
  </Step>
</Steps>

## From Listings

<Steps>
  <Step title="Open Add listing">
    Open **Listings** in the sidebar and choose **Add listing**. The form has three steps:
    **Assets**, **Describe**, and **Review**.
  </Step>

  <Step title="Attach assets">
    On **Assets**, choose **Add** and pick a kind:

    * **HUD tasksets**: attach tasksets your team owns on HUD. The environments they run on are
      attached with them.
    * **Codebases**: connect GitHub, GitLab, or Bitbucket in
      [Connectors](/sell/connect-your-accounts) and pick a repository, or upload a repository
      archive.
    * **Raw data**: choose a content tag and upload a ZIP.

    One listing can mix these kinds. Standalone HUD environments and robotics data cannot be
    added to a listing.

    With a codebase archive you can also attach a `manifest.toml`: copy the prompt, run it with a
    coding agent inside the repository, and attach the file it writes. The manifest is optional.
    If you attach one, its pull request count must match the pull requests captured in the
    archive.

    <Note>
      Uploads accept `.zip` only, up to 50 GB per file. A codebase archive's repository can be at
      most 20 GB.
    </Note>
  </Step>

  <Step title="Tag domains and set prices">
    Still on **Assets**, choose at least one domain tag for every asset and set its prices. Tags
    classify the listing in the catalog and drive the price guidance you see while pricing.

    | Price | Applies to |
    | - | - |
    | **Per Task** | One rate for every task across the listing's tasksets. |
    | **Per Environment** | One rate for every environment the tasksets run on. |
    | **Per repository** | Each codebase, priced on its own. |
    | **Per Bundle** | Each Raw data ZIP, priced on its own. |
    | **Sample price** | What a buyer pays for a [sample](/buy/try-a-sample). Required once the listing's tasksets hold at least two runnable tasks; otherwise the listing offers no sample. |

    The buy-now total is the sum of these, shown as **Buy now total**.

    <Note>
      Price guidance bands are advisory only. They never block saving or submitting.
    </Note>
  </Step>

  <Step title="Describe the listing">
    On **Describe**, write the title (up to 60 characters), one-liner (up to 100 characters), and
    listing description (up to 8,192 characters of plain English text; accented letters,
    non-Latin scripts, and emoji count as several characters each).
  </Step>

  <Step title="Review and submit">
    On **Review**, confirm **I confirm ownership and licensing rights for this data**, then
    choose **Submit for review**.
  </Step>
</Steps>

There is no separate NDA to sign: submitting relies on the
[Mutual NDA](/overview/glossary#nda) you accepted to open the workspace. Submitting starts
[quality checks](/sell/listings/quality-checks).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.