> 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/index.md).

# Nexus Home

Build, run, pay for, and verify agentic workflows on Sui with Nexus.

The documentation for Nexus — the on-chain protocol and off-chain runtime for building, running, paying for, and verifying agentic workflows on Sui.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><a href="/talus-docs-v2.1.0/guides/getting-started.md"><strong>Getting Started</strong></a><br>Install the CLI and configure a provider-supplied authenticated network artifact.</td><td><a href="https://3395888576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLPrUNT846cHDCVQcRD3f%2Fuploads%2Fgit-blob-a17f2f22623afc88077d7ef62b83c31f573c892f%2Fcard1.png?alt=media">card1.png</a></td></tr><tr><td><a href="/talus-docs-v2.1.0/concepts/00-protocol-overview.md"><strong>Protocol Overview</strong></a><br>Build the mental model from Agent and business state through Tools, trust, execution, payment, Leaders, discovery, and upgrades.</td><td><a href="https://3395888576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLPrUNT846cHDCVQcRD3f%2Fuploads%2Fgit-blob-ca546bcc189bd379770dd874dc93ae66dcdf0bb3%2Fcard2.png?alt=media">card2.png</a></td></tr><tr><td><a href="/talus-docs-v2.1.0/guides/guides.md"><strong>Guides</strong></a><br>Follow task-oriented guides for building, registering, executing, settling, upgrading, and debugging agents and Tools.</td><td><a href="https://3395888576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLPrUNT846cHDCVQcRD3f%2Fuploads%2Fgit-blob-941dddc8bf7946c9791d44d18c411ee1063b865b%2Fcard4.png?alt=media">card4.png</a></td></tr><tr><td><a href="/talus-docs-v2.1.0/reference/reference.md"><strong>Reference</strong></a><br>Look up exact public Move, SDK, CLI, Toolkit, and hosted API surfaces.</td><td><a href="https://3395888576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLPrUNT846cHDCVQcRD3f%2Fuploads%2Fgit-blob-99db99c8854f3beb6e4bce6d0e076753232eb766%2Fcard3.png?alt=media">card3.png</a></td></tr><tr><td><a href="/talus-docs-v2.1.0/faq/01-overview.md"><strong>FAQ Overview</strong></a><br>Find fast answers by concern.</td><td><a href="https://3395888576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLPrUNT846cHDCVQcRD3f%2Fuploads%2Fgit-blob-832d7571d6b128e06cd9c9a7b9191d616618cd69%2Fcard5.png?alt=media">card5.png</a></td></tr><tr><td><a href="/talus-docs-v2.1.0/glossary/glossary.md"><strong>Glossary</strong></a><br>Use the canonical Nexus vocabulary.</td><td><a href="https://3395888576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLPrUNT846cHDCVQcRD3f%2Fuploads%2Fgit-blob-289694eb2c001bee2f73f48ff02148680b70797c%2Fcard6.png?alt=media">card6.png</a></td></tr></tbody></table>

## Use Nexus coding skills

Give your AI coding assistant Nexus-specific guidance for building Tools and TAPs, creating API applications, or diagnosing executions and payments. From your project directory, install the skills with:

```bash
npx skills add Talus-Network/skills
```

Select the skills and assistant in the installer, then follow [Use Nexus Coding Skills](/talus-docs-v2.1.0/guides/getting-started/coding-skills.md) for prerequisites, skill selection, and example usage.

## Site map

This site is organized around seven sections, from interface choice and mental model to exact API:

* [**Concepts**](/talus-docs-v2.1.0/concepts/00-protocol-overview.md) — the connected mental model from Agent and business state through Tools, verifiers, DAG execution, payment, Leaders, registries, authorization, signed communication, result resolution, scheduling, priority fees, and upgrades.
* [**Guides**](/talus-docs-v2.1.0/guides/guides.md) — task-oriented tutorials grouped by getting started, agent authoring, Talus Agent Package (TAP) development, Tool development, package/Protocol upgrades, and DAG construction.
* [**Nexus SDK**](/talus-docs-v2.1.0/guides/sdk.md) — integrate directly with Nexus objects, Sui RPC, typed events, and transaction builders from Rust.
* [**Reference**](/talus-docs-v2.1.0/reference/reference.md) — the exact API surface: the Move packages, the SDK, the toolkit runtime, and the CLI.
* [**FAQ**](/talus-docs-v2.1.0/faq/01-overview.md) — fast, grounded answers organized by concern.
* [**Glossary**](/talus-docs-v2.1.0/glossary/glossary.md) — the canonical term definitions the rest of the site builds on.

## Actors

The old SDK overview distinguished the people using the system. Keep that map in mind while navigating the new site:

* **Nexus maintainer.** Core team member who maintains the Nexus codebase, generated reference, and public package deployments.
* **Tool developer.** Builder who develops off-chain HTTP tools or on-chain Move tools to be registered in the tool registry and called by DAG vertices.
* **Agent developer.** Builder who creates DAGs, defines agent packages or TAP package skills, registers those skills against an agent, and decides how payment, scheduling, fixed tools, and verification should work.
* **Agent user.** End user or application calling a registered skill or default-agent DAG through a client, CLI, or app-specific interface.


---

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