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

# nexus tool

**Audience:** Nexus CLI users and integrators.

**Command:** `nexus tool`.

**Generated from:** Nexus CLI `v2.1.1` release executable at commit `08bfe76e726922ce512d623fbc1d2e1bd786bcd4` (generated inventory preserved below).

This page is the complete help tree for `nexus tool`. Global output flags can appear after the family or nested subcommand.

### Tool economy contract

The `nexus tool cashier` tree inspects accepted policies and the completed Invocation/deposit inbox, opens or closes finite-credit and time-pass issuance, buys or issues entitlements, and collects policy-homogeneous finalized Invocations or generic deposits. New Tool registration already accepts FixedPrice; change its price through top-level `nexus tool set-invocation-cost` rather than a cashier configuration command. Cashier owner mutations require `CloneableOwnerCap<OverToolCashier>`; registry endorsement requires `ToolRegistryAdminCap`; Tool lifecycle and result-verifier configuration use `CloneableOwnerCap<OverTool>`. The registration-time `MetaSchema` is immutable, so an incompatible FQN/module/schema/output/witness contract requires a new Tool identity. Callers select accepted policies and supply their exact entitlement object when required. See [Invocation policy and settlement model](/concepts/06-payment-vaults-reserves-and-settlement.md#invocation-policy-and-settlement-model).

Verify the selected binary’s `nexus tool cashier --help`, generated bindings, cashier capability, package IDs, and transaction effects before executing a command against a deployment.

#### Historical c8ff compatibility

The historical c8ff CLI/SDK exposed `cashier expiry` and `cashier limited-invocations`; those commands are absent from the documented CLI. Use those names only when maintaining an explicitly pinned historical client, and never substitute them for Invocation identity, receipts, entitlement/refund state, or policy-revenue collection.

#### `nexus tool`

```
Manage Nexus Tools

Usage: nexus tool [OPTIONS] <COMMAND>

Commands:
  new                  Create a new tool scaffolding with the specified name and template.
  validate             Validate a tool based on its type.
  register             Register a tool based on its type.
  cashier              Manage Tool economic policies and entitlements
  unregister           Unregister a Tool from live protocol lookup
  update-url           Update the HTTP endpoint of an offchain Tool
  update-metadata      Update the description of a Tool
  migrate-package      Update the package of an onchain Tool
  update-timeout       Update the execution timeout of a Tool
  set-invocation-cost  Set the invocation price of a Tool
  configure-verifier   Configure Tool response verification
  claim-collateral     Claim collateral for a tool identified by its FQN.
  list                 List all registered tools.
  inspect              Inspect a registered tool by FQN. Returns the derived Tool and ToolCashier
                       IDs and the complete semantic tool record when it exists.
  auth                 Manage tool auth for signed HTTP.
  help                 Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool new`

```
Create a new tool scaffolding with the specified name and template.

Usage: nexus tool new [OPTIONS] --name <NAME> --description <DESCRIPTION> --template <TEMPLATE>

Options:
  -n, --name <NAME>                  The name of the tool to create
      --description <DESCRIPTION>    The user facing behavior description stored with the Tool
  -t, --template <TEMPLATE>          The Nexus Tool template to use [possible values: rust, move]
      --mode <MODE>                 Move execution mode [default: standard; possible values: standard, workflow-authorization]
  -d, --target <TARGET>              The target directory to create the tool in [default: ./]
  -h, --help                         Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

For `--template move`, Standard mode has the `UIDRequirements, OnchainToolResult` prefix. Use `--mode workflow-authorization` to prepend `ProvenValue<AgentVertexAuthorization>` and implement its verification before mutation. `--mode` is rejected with `--template rust`. Move scaffolds use MVR dependencies, `version = "1.0.0"`, and `edition = "2024.alpha"`, without an `[addresses]` table.

#### `nexus tool validate`

```
Validate a tool based on its type.

Usage: nexus tool validate [OPTIONS] <COMMAND>

Commands:
  offchain  Validate an offchain tool
  onchain   Validate an onchain tool
  help      Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool validate offchain`

```
Validate an offchain tool

Usage: nexus tool validate offchain [OPTIONS] --url <URL>

Options:
  -u, --url <URL>  The URL of the offchain tool to validate
  -h, --help       Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool validate onchain`

{% hint style="info" %}
This validator fetches a registered on-chain Tool by FQN, resolves its live `execute` and `Output` schemas, normalizes them into `MetaSchema`, and compares both the registered schema and Standard versus WorkflowAuthorization mode. Success reports the Tool state, or `{"valid":true,"fqn":...,"tool":...}` with `--json`.
{% endhint %}

It does not prove package lineage, UpgradeCap custody, dependency linkage, witness ownership, or business invariants. Use the [on-chain Tool candidate-verification checklist](/guides/tool-development/build-onchain-tool-vertex-and-upgrade.md#verify-the-candidate) when those proofs are required.

```
Validate an onchain tool

Usage: nexus tool validate onchain [OPTIONS] --ident <FQN>

Options:
  -i, --ident <FQN>  The FQN of the registered onchain tool to validate
  -h, --help           Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool register`

```
Register a tool based on its type.

Usage: nexus tool register [OPTIONS] <COMMAND>

Commands:
  offchain  Register an offchain tool
  onchain   Register an onchain tool
  help      Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool register offchain`

```
Register an offchain tool

Usage: nexus tool register offchain [OPTIONS]

Options:
  -u, --url <URL>                    The URL of the offchain tool. Required unless --from-meta is
                                     provided.
      --from-meta <FILE|->           Path to a JSON file containing tool metadata (as produced by
                                     the tool binary's --meta flag), or '-' to read from stdin.
                                     Skips the live HTTP validation step.
  -c, --collateral-coin <OBJECT_ID>  The US collateral coin object ID. First owned Coin<US> object
                                     is chosen if not present.
  -i, --invocation-cost <MIST>       The price of one tool invocation in MIST. [default: 0]
      --batch                        Should all tools on a webserver be registered at once?
                                     Incompatible with --from-meta.
      --no-save                      If this flag is set, the tool owner caps will not be saved to
                                     the local config file.
  -h, --help                         Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool register onchain`

```
Register an onchain tool

Usage: nexus tool register onchain [OPTIONS] --package <ADDRESS> --module <MODULE> --tool-fqn <FQN> --description <DESCRIPTION> --tool-witness-id <OBJECT_ID>

Options:
  -p, --package <ADDRESS>            The onchain tool package address
  -m, --module <MODULE>              The onchain tool module name
  -t, --tool-fqn <FQN>               The fully qualified name (FQN) for this tool.
  -d, --description <DESCRIPTION>    Description of what the tool does.
  -i, --timeout <DURATION>           The timeout duration for the tool execution. Defaults to 5
                                     seconds. Value must be between 1 second and 2 minutes.
                                     [default: 5s]
  -w, --tool-witness-id <OBJECT_ID>  The tool witness object ID used as the on-chain execution stamp
                                     locator.
  -c, --collateral-coin <OBJECT_ID>  The US collateral coin object ID. First owned Coin<US> object
                                     is chosen if not present.
      --invocation-cost <MIST>       Cost of one tool invocation in MIST [default: 0]
      --no-save                      If this flag is set, the tool owner caps will not be saved to
                                     the local config file.
  -h, --help                         Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool cashier`

Manage one Tool's accepted Invocation policies and completed accounting inbox.

Merged commands include:

* `inspect` — show accepted policies, configured terms, and canonical Tool economy.
* `inbox` — list completed Invocations and prepaid deposits waiting for collection.
* `collect-invocations` — collect one policy-homogeneous batch under the ToolCashier owner capability.
* `collect-deposits` — collect one batch of prepaid sale deposits under owner authority.
* `access` — inspect the configured beneficiary's access state.
* `finite-credits enable|close-issuance|open-issuance|update-terms|buy|issue|restore-refund` — manage finite-credit entitlements and restore one refunded Invocation.
* `time-pass enable|close-issuance|open-issuance|update-terms|buy|issue` — manage immutable time-pass entitlements.

The collection commands take an exact Tool FQN and one or more repeated exact Invocation or deposit IDs; owner capability and recipient flags are selected by the command's help:

```
nexus tool cashier collect-invocations --tool-fqn <FQN> --invocation-id <OBJECT_ID> --invocation-id <OBJECT_ID> [--cashier-admin <OBJECT_ID>] [--recipient <ADDRESS>]
nexus tool cashier collect-deposits --tool-fqn <FQN> --deposit-id <OBJECT_ID> --deposit-id <OBJECT_ID> [--cashier-admin <OBJECT_ID>] [--recipient <ADDRESS>]
```

The finite-credit recovery command is `nexus tool cashier finite-credits restore-refund --tool-fqn <FQN> --invocation-id <OBJECT_ID>`.

Owner configuration and collection require the ToolCashier administration capability `CloneableOwnerCap<OverToolCashier>`; registry endorsement is a separate `ToolRegistryAdminCap` operation. `collect-invocations` accepts one or more repeated exact Invocation IDs in one policy-homogeneous batch; `collect-deposits` accepts one or more repeated exact `CashierDeposit` IDs, which carry no policy field and therefore do not share that constraint. Closing issuance stops new buy/issue operations but preserves existing Credits and TimePass objects; `update-terms` applies to future objects. A caller may buy or use an accepted entitlement without those owner capabilities, but its `beneficiary` must match the Invocation payment source. Every authorization and refund remains tied to the exact Invocation identity.

Finite-credit `buy` requires open issuance, uses the configured `minimum_credits`/`maximum_credits`, and charges `price_per_credit × credits`; owner `issue` requires open issuance and the same bounds but does not charge the offer price. One canonical shared Credits account is derived from the ToolCashier and beneficiary, and its mutable remaining balance serializes authorization. There is no split, join, or refund-manager API. Any matching active Execution may attempt a shared Credits or frozen TimePass authorization, and source, remaining-unit, and validity checks can deny or require retry.

For TimePass, `buy` is bounded by the accepted `price_per_ms`, `minimum_duration_ms`, and `maximum_duration_ms`, while owner `issue` requires open issuance and only checks `valid_from_ms < valid_until_ms`; both returned passes are frozen by the SDK builders, whereas raw Move callers must freeze them themselves. Existing Credits and TimePass objects retain their Tool/Cashier identity and beneficiary or interval across URL/package changes and same-object re-registration, but Invocation admission still checks matching Tool/Cashier IDs, accepted policy, and payment source; registry endorsement and RegisteredKey/External result-verifier setup are separate operational/verification steps that may need renewal after registration state changes.

See [Invocation policy and settlement model](/concepts/06-payment-vaults-reserves-and-settlement.md#invocation-policy-and-settlement-model) for policy terms, receipts, timeout refund, and collection invariants.

#### `nexus tool unregister`

```
Unregister a tool identified by its FQN.

Usage: nexus tool unregister [OPTIONS] --tool-fqn <FQN>

Options:
  -t, --tool-fqn <FQN>         The FQN of the tool to unregister.
  -o, --owner-cap <OBJECT_ID>  The OwnerCap<OverTool> object ID that must be owned by the sender.
  -y, --yes                    Skip the confirmation prompt
  -h, --help                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool configure-verifier`

```
Configure the verifier supported by an offchain Tool.

Usage: nexus tool configure-verifier [OPTIONS] <COMMAND>

Commands:
  registered-key  Configure the built-in RegisteredKey verifier for an offchain Tool.
  external        Configure a public External verifier for an offchain Tool.
  help            Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool configure-verifier registered-key`

```
Configure the built-in RegisteredKey verifier for an offchain Tool.

Usage: nexus tool configure-verifier registered-key [OPTIONS] --tool-fqn <FQN>

Options:
  -t, --tool-fqn <FQN>
  -o, --owner-cap <OBJECT_ID>  OwnerCap<OverTool> object ID (defaults to saved CLI config for this
                               tool).
  -h, --help                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool configure-verifier external`

```
Configure a public External verifier for an offchain Tool.

Usage: nexus tool configure-verifier external [OPTIONS] --tool-fqn <FQN> --package <PACKAGE_ID> --module <MODULE> --function <FUNCTION> --verifier-object <OBJECT_ID>...

Options:
  -t, --tool-fqn <FQN>
  -o, --owner-cap <OBJECT_ID>           OwnerCap<OverTool> object ID (defaults to saved CLI config
                                        for this tool).
  -p, --package <PACKAGE_ID>
  -m, --module <MODULE>
  -f, --function <FUNCTION>
      --verifier-object <OBJECT_ID>...
  -h, --help                            Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool claim-collateral`

```
Claim collateral for a tool identified by its FQN.

Usage: nexus tool claim-collateral [OPTIONS] --tool-fqn <FQN>

Options:
  -t, --tool-fqn <FQN>         The FQN of the tool to claim the collateral for.
  -o, --owner-cap <OBJECT_ID>  The OwnerCap<OverTool> object ID that must be owned by the sender.
  -h, --help                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool set-invocation-cost`

```
Set the price of one tool invocation in MIST

Usage: nexus tool set-invocation-cost [OPTIONS] --tool-fqn <FQN> --cost <MIST>

Options:
  -t, --tool-fqn <FQN>             The fully qualified name (FQN) of the tool.
      --cost <MIST>                 The invocation price of the Tool in MIST.
      --cashier-admin <OBJECT_ID>  The Tool cashier admin capability object ID. Uses the saved
                                   capability when omitted.
  -h, --help                       Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool list`

```
List all registered tools.

Usage: nexus tool list [OPTIONS]

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool inspect`

```
Inspect a registered tool by FQN. Returns the derived Tool and ToolCashier IDs and the complete
semantic tool record when it exists.

Usage: nexus tool inspect [OPTIONS] --tool-fqn <FQN>

Options:
  -t, --tool-fqn <FQN>  The FQN of the tool to inspect.
  -h, --help            Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool auth`

```
Manage tool auth for signed HTTP.

Usage: nexus tool auth [OPTIONS] <COMMAND>

Commands:
  keygen                  Generate a new Ed25519 message-signing key for a tool.
  register-key            Register (or rotate) a tool message-signing key on-chain.
  list-keys               List all registered message-signing keys for a tool.
  export-allowed-leaders  Export a leader allowlist file for tool-side verification (no RPC at
                          runtime).
  sync-allowed-leaders    Sync an allowed leaders allowlist file from on-chain network_auth
                          (polling).
  help                    Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool auth keygen`

```
Generate a new Ed25519 message-signing key for a tool.

Usage: nexus tool auth keygen [OPTIONS]

Options:
      --out <OUT>
          Write the generated keypair JSON to this path. The output contains both `private_key_hex`
          and `public_key_hex`.

  -h, --help
          Print help (see a summary with '-h')

Output:
      --json
          Emit machine readable JSON

  -v, --verbose...
          Increase diagnostic detail

  -q, --quiet...
          Show errors only
```

#### `nexus tool auth register-key`

```
Register (or rotate) a tool message-signing key on-chain.

Usage: nexus tool auth register-key [OPTIONS] --tool-fqn <FQN> --signing-key <KEY_OR_PATH>

Options:
  -t, --tool-fqn <FQN>             The fully qualified name (FQN) of the tool.
  -o, --owner-cap <OBJECT_ID>      OwnerCap<OverTool> object ID (defaults to saved CLI config for
                                   this tool).
  -k, --signing-key <KEY_OR_PATH>  Tool Ed25519 private key (hex/base64/base64url) OR a path to a
                                   file containing it.
      --description <TEXT>         Optional description bytes stored on the key binding.
      --skip-if-active             Skip registration if the same public key is already the active
                                   key (idempotent). Useful in CI to avoid re-registering an
                                   unchanged key.
  -h, --help                       Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool auth list-keys`

```
List all registered message-signing keys for a tool.

Usage: nexus tool auth list-keys [OPTIONS] --tool-fqn <FQN>

Options:
  -t, --tool-fqn <FQN>  The fully qualified name (FQN) of the tool.
  -h, --help            Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool auth export-allowed-leaders`

```
Export a leader allowlist file for tool-side verification (no RPC at runtime).

Usage: nexus tool auth export-allowed-leaders [OPTIONS] --out <OUT>

Options:
      --all                     Export allowlist entries for all leaders registered in network_auth
                                (recommended).
      --leader <LEADER_CAP_ID>  One or more leader capability IDs (`leader_cap::OverNetwork` object
                                IDs) to include
      --out <OUT>               Output path for the allowlist JSON file.
  -h, --help                    Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool auth sync-allowed-leaders`

```
Sync an allowed leaders allowlist file from on-chain network_auth (polling).

Usage: nexus tool auth sync-allowed-leaders [OPTIONS] --out <OUT>

Options:
      --out <OUT>            Output path for the allowlist JSON file.
      --interval <DURATION>  Polling interval (e.g. 500ms, 5s, 2m, 1h). [default: 30s]
      --once                 Sync once and exit.
  -h, --help                 Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool update-url`

Update HTTP endpoint for an offchain Tool.

```
Update the HTTP endpoint of an offchain Tool

Usage: nexus tool update-url [OPTIONS] --tool-fqn <FQN> --url <URL>

Options:
  -t, --tool-fqn <FQN>
  -u, --url <URL>
  -o, --owner-cap <OBJECT_ID>
  -h, --help                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool update-metadata`

Update the description for a Tool.

```
Update the description of a Tool

Usage: nexus tool update-metadata [OPTIONS] --tool-fqn <FQN> --description <TEXT>

Options:
  -t, --tool-fqn <FQN>
  -d, --description <TEXT>
  -o, --owner-cap <OBJECT_ID>
  -h, --help                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool migrate-package`

Update the package for an onchain Tool.

```
Update the package of an onchain Tool

Usage: nexus tool migrate-package [OPTIONS] --tool-fqn <FQN> --package <PACKAGE_ID>

Options:
  -t, --tool-fqn <FQN>
  -p, --package <PACKAGE_ID>
  -o, --owner-cap <OBJECT_ID>
  -h, --help                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus tool update-timeout`

```
Update a tool's timeout duration.

Usage: nexus tool update-timeout [OPTIONS] --tool-fqn <FQN> --timeout <DURATION>

Options:
  -t, --tool-fqn <FQN>         The FQN of the tool to update the timeout for.
  -o, --owner-cap <OBJECT_ID>  The OwnerCap<OverTool> object ID that must be owned by the sender.
  -i, --timeout <DURATION>     The new timeout duration for the tool execution. Value must be
                               between 1 second and 2 minutes.
  -h, --help                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```


---

# 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/cli/tool.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.