# Dataset

URL: https://docs.hanzo.ai/docs/cli/dataset

> The `hanzo dataset` commands.

Also for this capability: [API](https://docs.hanzo.ai/docs/openapi/dataset) · **CLI** · [MCP](https://docs.hanzo.ai/docs/mcp-tools/dataset) · [SDKs](https://docs.hanzo.ai/docs/sdks)

The per-org dataset plane of /v1/risk: a dataset is a VERSIONED, IMMUTABLE snapshot of one tenant's own event surface, and this is where it is declared, materialised, described, exported and disposed of.

[API reference →](https://docs.hanzo.ai/docs/openapi/dataset)

```bash
hanzo dataset list
```

Every command takes `--json` for the raw response and `--help` for its own flags. Sign in once with `hanzo auth login`; the commands below use that session, and the org they act in is the one it carries.

| Command                            | What it does                                                                      |
| ---------------------------------- | --------------------------------------------------------------------------------- |
| `hanzo dataset create`             | Declare the next version of a dataset                                             |
| `hanzo dataset export <name>`      | Read a version's rows back, one page at a time                                    |
| `hanzo dataset get <name>`         | Describe every version of one dataset                                             |
| `hanzo dataset lineage <name>`     | Show where a version's rows came from, and whether that can still be demonstrated |
| `hanzo dataset list`               | List this org's datasets                                                          |
| `hanzo dataset materialize <name>` | Materialise the declared version into immutable rows                              |
| `hanzo dataset rm <name>`          | Dispose of one dataset and every version of it                                    |