> 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/reference/move/nexus_registry.md).

# nexus\_registry

Registry modules for agents, leaders, network-auth keys, priority fees, and registered-key verification.

**Generated from:** the public Nexus Move Packages interface for the selected deployment (generated — do not hand-edit module signatures).

### Modules

* [agent\_registry](/reference/move/nexus_registry/agent_registry.md) - Agent registry records, skill registration, updates, and lookup helpers.
* [era](/reference/move/nexus_registry/era.md) - Package era and protocol-version markers.
* [leader](/reference/move/nexus_registry/leader.md) - Leader registry state, staking, activation, selection, suspension, and metadata helpers.
* [leader\_cap](/reference/move/nexus_registry/leader_cap.md) - Leader capability types and network authority helpers.
* [leader\_slashing](/reference/move/nexus_registry/leader_slashing.md) - Internal capability marker used by the public Leader registry slashing flow; it exposes no application-callable helper here.
* [main](/reference/move/nexus_registry/main.md) - Package initialization marker; use the public callable registry modules rather than treating this page as an application entrypoint.
* [network\_auth](/reference/move/nexus_registry/network_auth.md) - Network-auth identity, key registration, rotation, and signed HTTP key binding.
* [priority\_fee\_vault](/reference/move/nexus_registry/priority_fee_vault.md) - Priority SUI deposits, collection/shares, US liquidity, and withdrawal.
* [registered\_key\_verifier](/reference/move/nexus_registry/registered_key_verifier.md) - Registered-key verifier method integration.


---

# 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/reference/move/nexus_registry.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.