> ## 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.

# Add assets

> Import codebases, tasks, and Raw data into Inventory, with or without their data.

Open **Inventory** and choose **Add asset**. Codebases and Raw data land under **Ungrouped** until
you [move them into a group](/sell/inventory/overview#groups); imported tasks land in a group
named after their taskset.

## Codebases

Choose **Codebases**, then one of three ways in.

<Tabs>
  <Tab title="Import from a forge">
    Connect GitHub, GitLab, or Bitbucket (see [Connect your accounts](/sell/connect-your-accounts)),
    select the repositories, and choose **Import**. Each repository becomes its own asset with its
    data linked.
  </Tab>

  <Tab title="Upload as files">
    Choose **Upload as files**. A codebase upload needs a specific archive layout, so copy the
    prompt into a coding agent; it builds the zip and uploads it.
  </Tab>

  <Tab title="Add in bulk via API">
    Register codebases you could supply without uploading any code. See
    [below](#add-in-bulk-via-api).
  </Tab>
</Tabs>

You can also add a repository from [Estimations](/sell/estimate-your-codebase) with
**Add to inventory**.

## Tasks

Choose **Tasks**, then **hud.ai**. In **Import tasks**, pick the **Type** every imported task gets
(Coding, Finance, Legal or General; quality checks run per type, so the import waits until you
choose), then select a taskset to import every task in it, or expand one and pick individual
tasks, and choose **Import**. Each task becomes its own asset, on its latest version, in a group
named after its taskset. Tasks without a version are skipped. The type shows in the **Tasks** view
and on the asset, where you can change it.

Each imported task also brings what the platform knows about its version: the models that ran
on it with their pass\@k, the QA agents that checked it and their verdicts, and whether its
environment is built. The **Tasks** view shows them in the **Traces**, **QA** and **Env** columns
and filters on them (**Traces**, **QA results**, **Environment**, **Ran on model**, **QA agent**);
the asset page lists every model and agent in its **QC** card. This is read once at import;
**Refresh QC** in the **Tasks** view header reads it again for every task in your inventory and
shows when it last did.

<Note>
  Tasks cannot be listed for sale from Inventory yet. To sell them, list their taskset from
  [Listings](/sell/listings/create-a-listing#from-listings).
</Note>

## Raw data

Choose **Raw data**, then drop a ZIP on **Drop or browse .zip** or click it to browse. The ZIP is
stored as it is; any files and folders are fine. Dropping a ZIP anywhere on the inventory page does
the same.

A kind DataVendor no longer accepts shows as **Deprecated** in **Add asset** and cannot be
chosen.

## Harbor tasks

Harbor tasks are not imported here directly. **Harbor tasks** in **Add asset** opens HUD's guide to
importing them, [docs.hud.ai/v6/experimental/harbor](https://docs.hud.ai/v6/experimental/harbor).
Once they are on HUD, add them here as **Tasks**.

## Add in bulk via API

Adding in bulk registers what you could supply if a buyer appears, before you link its data.

<Steps>
  <Step title="Open the snippet">
    In **Add asset**, choose **Codebases**, then **Add in bulk via API**.
  </Step>

  <Step title="Register your codebases">
    On **Step 1: Register rows**, copy a snippet into your coding agent. It registers the codebases
    through the DataVendor API, up to 500 at a time, with a title, a description, and any metadata
    you already know. Each codebase appears in **Inventory** as **Proposed**, or **Incomplete**
    while metadata is still missing.
  </Step>

  <Step title="Link their data">
    When you are ready to attach the code, choose **Continue to step 2** (or **Link data** on a
    row in **Inventory**) and copy the **Step 2: Link data** snippet into your coding agent. It
    attaches a repository from GitHub, GitLab, or Bitbucket, or a ZIP, to each registered row.
    Then [list it for sale](/sell/listings/create-a-listing#from-inventory).
  </Step>
</Steps>

<Note>
  Step 1 registers metadata only; it does not upload any code.
</Note>

The snippet uses the same [vendor API](/sell/api/rest-api#codebases) you can call
directly: register repositories one at a time or in batches, and organize them into groups.

## Next

[Create a listing](/sell/listings/create-a-listing) from assets whose data is linked.


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