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

# Publishing datasets: storage, pipeline, and listing

> Upload a dataset, run the ADC processing pipeline to build a quality datacard, and publish it as a live listing agents can discover, trial, and buy.

Datasets are the core of the Sella marketplace. When you upload a dataset and submit it for processing, Sella runs it through a multi-stage pipeline that analyzes structure, scores quality, and builds a datacard — the record agents read before deciding to trial or buy your listing. Getting that pipeline right is the fastest path to a live, converting listing.

## Storage modes

How you store your dataset determines how buyers receive it. Choose the mode that matches your file size and delivery needs.

<CardGroup cols={2}>
  <Card title="Inline" icon="file-lines" href="/publishers/quality">
    Content is stored directly in the catalogue record. Best for small, structured datasets. `get_dataset` returns the full content in the response body.
  </Card>

  <Card title="Asset-backed" icon="cloud" href="/publishers/quality">
    Files live in S3-compatible object storage. `get_dataset` returns a short-lived **presigned download URL** instead of the raw content. Best for large files.
  </Card>
</CardGroup>

## The processing pipeline

When you submit a dataset for analysis, it moves through a `process` stage that produces its datacard. Each step builds on the last — skip or rush one and the datacard suffers.

<Steps>
  <Step title="Structural analysis">
    Sella detects schema, formats, and completeness — the objective shape of your data. This feeds the `structural` section of your datacard.
  </Step>

  <Step title="Quality judging">
    An evaluation pass scores quality signals including task fitness, synthetic probability, and adequacy checks. The results populate the `judge` section of your datacard. See [Quality & datacards](/publishers/quality) for a full breakdown.
  </Step>

  <Step title="Trial generation">
    Sella builds the preview payload agents see when they call `try_dataset` — a faithful, representative sample, never your full content. This lands in the `trial` section of your datacard.
  </Step>
</Steps>

The final result is a `dataCard` object on your listing. Agents read it before purchasing, so a strong datacard is your most effective sales tool.

## ADC — the data contract

Sella evaluates every listing against the **Application Data Contract (ADC)**: the metadata specification that describes provenance, schema, licensing, and quality. Meeting the ADC cleanly earns you a green [`qualityStatus`](/publishers/quality) and better placement in agent search results. Gaps in provenance or licensing are the most common reasons listings stall in `manual_review`.

## Publish states

Your listing moves through a defined set of states from first save to public visibility. Only two states are visible to agents.

| State           | Meaning                                                                         |
| --------------- | ------------------------------------------------------------------------------- |
| `draft`         | Saved but not yet submitted for processing. Invisible to agents.                |
| `process`       | Analysis is running and your datacard is being built. Invisible to agents.      |
| `manual_review` | Listed but flagged for a human moderator. Visible in public flows once cleared. |
| `live`          | Fully public — discoverable, trialable, and purchasable by any agent.           |

<Note>
  Only `live` and `manual_review` listings appear in public listing and search flows. A dataset in `draft` or `process` is completely invisible to agents until it advances.
</Note>

## Reprocessing

Improved your data or metadata? Re-run analysis at any time to rebuild the datacard from scratch, or trigger a re-score to refresh quality signals without re-uploading the underlying file. Updated signals apply immediately to your live listing — there's no cooldown period.

## What makes a listing sell

<AccordionGroup>
  <Accordion title="Name and describe for search" icon="magnifying-glass">
    Agents filter on keywords and `required_fields`. Put real column names and concrete use cases in your title and description — not marketing language. If agents can't find you, they can't buy from you.
  </Accordion>

  <Accordion title="Make the preview honest and representative" icon="eye">
    Agents [trust the preview over the scores](/publishers/quality). A clean, representative trial sample converts far better than an inflated quality score. Show a real slice of your data, not a cherry-picked best row.
  </Accordion>

  <Accordion title="State provenance and license plainly" icon="scroll">
    Buyers actively filter out ambiguous licensing. A clear `licenseType` and explicit provenance statement widen your buyer pool and reduce the chance of landing in `manual_review`.
  </Accordion>

  <Accordion title="Price to the tier" icon="tag">
    Match your [tier and price](/publishers/pricing) to the real value and specificity of your data. Overpriced commodity data sits; well-priced specialist data moves.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Quality & datacards" icon="badge-check" href="/publishers/quality">
    Understand every signal behind your listing's grade and how to improve them.
  </Card>

  <Card title="Pricing & earnings" icon="coins" href="/publishers/pricing">
    Set a USDC price, understand the platform fee, and get paid out.
  </Card>
</CardGroup>