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

# Rust SDK

**Audience:** Nexus SDK integrators (Rust).

**Area:** SDK.

**Generated from:** Nexus SDK public API at release `v2.1.0` commit `45d397aafcfbeeeaf5032d5fb9fa5d99b3f36205`; the generated baseline is preserved and 2.1.0 additions below are source-verified.

This landing page and generated pages describe the documented SDK surface. For policy-backed Tool authorization and exact receipts, use [Invocation policy and settlement model](/talus-docs-v2.1.0/concepts/06-payment-vaults-reserves-and-settlement.md#invocation-policy-and-settlement-model); for runtime witness and rotation authority, use [Protocol Upgrades and Compatibility](/talus-docs-v2.1.0/concepts/14-protocol-upgrades-and-compatibility.md).

The generated pages record their exact source revision. Use [Pinned source installation](/talus-docs-v2.1.0/guides/getting-started/setup.md#pinned-checkout-and-install) for `v2.1.0`; Nexus mutations also require matching authenticated Nexus object bindings.

Rust SDK reference pages for constructing a `NexusClient` with configured `NexusObjects`, building transactions, calling workflow, scheduler, tool, network-fee, network-authentication, and Talus Agent Package (TAP) actions, and handling SDK types and errors.

For application-level direct SDK/RPC/PTB architecture, custody, event replay, and readback responsibilities, use the authored [Nexus SDK Integration](/talus-docs-v2.1.0/reference/sdk/integration.md) page. The HTTP REST/SSE/API-key product has its own [Nexus API reference](/talus-docs-v2.1.0/guides/nexus-api.md).

### Pages

* [Client construction and configuration](/talus-docs-v2.1.0/reference/sdk/client.md)
* [Crawler reads](/talus-docs-v2.1.0/reference/sdk/crawler.md)
* [Event ingestion](/talus-docs-v2.1.0/reference/sdk/events.md)
* [Workflow actions](/talus-docs-v2.1.0/reference/sdk/actions-workflow.md)
* [Scheduler actions](/talus-docs-v2.1.0/reference/sdk/actions-scheduler.md)
* [Tool actions](/talus-docs-v2.1.0/reference/sdk/actions-tool.md)
* [Network fee actions](/talus-docs-v2.1.0/reference/sdk/actions-network.md)
* [Network auth actions](/talus-docs-v2.1.0/reference/sdk/actions-network-auth.md)
* [TAP actions](/talus-docs-v2.1.0/reference/sdk/actions-tap.md)
* [Protocol resolution and compatibility](/talus-docs-v2.1.0/reference/sdk/protocol.md)
* [Transactions](/talus-docs-v2.1.0/reference/sdk/transactions.md)
* [Types](/talus-docs-v2.1.0/reference/sdk/types.md)
* [Errors](/talus-docs-v2.1.0/reference/sdk/errors.md)
* [Nexus SDK Integration](/talus-docs-v2.1.0/reference/sdk/integration.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/talus-docs-v2.1.0/reference/sdk.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.