> 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/guides/getting-started.md).

# Getting Started

{% hint style="info" %}
**Audience:** Nexus adopters and integrators.

**Goal:** Orient a new developer to the prerequisites and first runnable path before building an Agent or Tool.
{% endhint %}

### Coding assistant setup

If you use a coding assistant, [install Nexus coding skills](/guides/getting-started/coding-skills.md) for task-specific guidance on Tool and TAP development, API applications, execution diagnosis, and payment tracking.

### Prerequisites

-Homebrew for the preferred Nexus CLI path. Rust/Cargo when adding the SDK or Toolkit to a Rust application, or when using the verified source CLI fallback.

* A Bash/POSIX-compatible shell plus Git, `jq`, `curl`, and coreutils-compatible `sha256sum`.
* Node.js 18 or later when following the hosted Nexus API tutorial or its React example.
* Nexus CLI, SDK, and Toolkit `2.1.1` and matching authenticated Nexus network objects supplied by Talus.
* The versioned Testnet TGE manifest documented in Setup for Talus token/faucet discovery.
* A protected Sui Testnet wallet with separate owned SUI coins for faucet exchange value and transaction gas.

#### First runnable objective

Complete [Developer Setup](/guides/getting-started/setup.md): install the verified CLI 2.1.1 with Homebrew and exact SDK/Toolkit 2.1.1 from crates.io, or download the verified binaries from GitHub; then checksum/configure the matching Nexus objects, configure Sui Testnet, protect the wallet, checksum and validate the versioned token/faucet manifest, dry-run the `$US` exchange, and verify the resulting balance. Nexus mutations remain blocked until the provider-approved protected signer path is also supplied.

Do not begin wallet-signed Agent or Tool mutations until the authenticated release tag is installed, the CLI can read matching Nexus objects, the protected signer path is approved, and the signer funding model is clear. Sui/Testnet reads, the documented `$US` faucet exchange, query-only documentation, and hosted Explorer/API inspection remain separate from that Nexus mutation readiness.

The math/chat DAG tutorials are conditional authoring exercises, not a provisioned first workflow. They require matching registered Tool FQNs and schemas supplied by your network operator or by Tools you build and register yourself; inspect those records before validating or scheduling an example DAG.

#### Next

Continue with [Agent Development](/guides/agent-usage.md) for an application identity, or [Tool Development](/guides/tool-development.md) for a callable capability. Before starting a TAP or on-chain Tool, complete [Prepare for On-Chain Development](/guides/getting-started/prepare-onchain-development.md).


---

# 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/guides/getting-started.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.