> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/talus-docs-v2.1.0/reference/cli/dag.md).

# nexus dag

**Audience:** Nexus CLI users and integrators.

**Command:** `nexus dag`.

**Generated from:** Nexus CLI `v2.1.0` release executable at commit `45d397aafcfbeeeaf5032d5fb9fa5d99b3f36205` (generated inventory preserved below).

This page is the complete help tree for `nexus dag`. Global output flags can appear after the family or nested subcommand.

```
Validate and publish Nexus DAGs

Usage: nexus dag [OPTIONS] <COMMAND>

Commands:
  inspect   Inspect published DAG entry groups and required inputs
  validate  Validate if a JSON file at the provided location is a valid Nexus DAG.
  publish   Publish a Nexus DAG spec file to the currently active Sui net. This command also
            performs validation on the file before publishing.
  help      Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus dag inspect`

```
Inspect published DAG entry groups and required inputs

Usage: nexus dag inspect [OPTIONS] --dag-id <OBJECT_ID>

Options:
  -d, --dag-id <OBJECT_ID>  Published DAG object ID
  -h, --help                Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus dag validate`

```
Validate if a JSON file at the provided location is a valid Nexus DAG.

Usage: nexus dag validate [OPTIONS] --path <PATH>

Options:
  -p, --path <PATH>  The path to the JSON file to validate
  -h, --help         Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus dag publish`

```
Publish a Nexus DAG spec file to the currently active Sui net. This command also performs validation
on the file before publishing.

Usage: nexus dag publish [OPTIONS] --path <PATH>

Options:
  -p, --path <PATH>  The path to the Nexus DAG spec file to publish
  -h, --help         Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talus.network/talus-docs-v2.1.0/reference/cli/dag.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.