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

# nexus\_interface

Public interface objects and typed values shared by agents, DAGs, payments, authorization, scheduling, and verification.

The payment page below is generated from the public Nexus Move Packages interface and includes the Invocation request, lock receipt, settlement receipt, and policy terms. A generated signature is source evidence; use matching SDK/CLI bindings, package IDs, and network effects before treating a command or hosted projection as available.

### Modules

* [agent](/talus-docs-v2.1.0/reference/move/nexus_interface/agent.md) - Agent identity, skill requirements, execution selection, vault receipts, scheduling policy, and agent-funded payment helpers.
* [authorization](/talus-docs-v2.1.0/reference/move/nexus_interface/authorization.md) - Agent skill and vertex authorization objects, grant release helpers, and worksheet matching.
* [dag](/talus-docs-v2.1.0/reference/move/nexus_interface/dag.md) - DAG object surfaces, graph bindings, per-vertex verifier mode starting `None`, and workflow metadata.
* [distributed\_event](/talus-docs-v2.1.0/reference/move/nexus_interface/distributed_event.md) - Distributed event wrapper and distribution metadata.
* [graph](/talus-docs-v2.1.0/reference/move/nexus_interface/graph.md) - Graph vertex, edge, port, output, entry-group, and failure-action data structures.
* [meta\_schema](/talus-docs-v2.1.0/reference/move/nexus_interface/meta_schema.md) - Tool input/output schema and port commitment types.
* [era](/talus-docs-v2.1.0/reference/move/nexus_interface/era.md) - Package era and protocol-version markers.
* [onchain\_tool\_result](/talus-docs-v2.1.0/reference/move/nexus_interface/onchain_tool_result.md) - Durable result object finalized by an on-chain Tool.
* [💳 nexus\_interface::payment](/talus-docs-v2.1.0/reference/move/nexus_interface/payment.md) - Payment sources, Invocation requests, exact lock/settlement receipts, reserves, charges, refunds, and public inspection helpers.
* [verifier](/talus-docs-v2.1.0/reference/move/nexus_interface/verifier.md) - Verifier modes, methods, proofs, transcripts, evidence, decisions, and verdict values.
* [version](/talus-docs-v2.1.0/reference/move/nexus_interface/version.md) - Interface version wrapper and version comparison helpers.


---

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