> 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/vision-explorer/search.md). # Vision Search {% hint style="info" %} **Audience:** Anyone holding an id, address, digest, or FQN and wanting the page for it. **Goal:** Know what the explorer search accepts and where each kind of input lands. {% endhint %} The search field lives in the header on every explorer route (and binds ⌘K). It does not search text; it classifies what you pasted and routes to the page for it. A 32-byte `0x…` value can be either an object ID or an account-shaped address; only chain lookup, returned object type, ownership, and address activity can classify it. If lookup proves neither, keep the result unresolved rather than routing by formatting alone. | You paste | Classified as | Lands on | | ----------------------- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | | `0x…` (32-byte hex) | object ID or wallet address candidate; formatting alone is ambiguous | Chain lookup resolves the Move type or account activity, then routes to the matching page | | 43–44 base58 characters | transaction digest | The **Transaction** page | | `domain.name@version` | tool FQN | That tool's page under **Tools** | For an object id, the explorer reads the object's type and routes by it rather than dropping everything on a generic viewer: | Move type | Page | | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | | `dag::DAG` | Workflow | | `execution::DAGExecution` | Execution | | `agent::Agent` | Agent | | `scheduler::Task` | Task | | `tool_registry::Tool` | Tool (by its FQN) | | `CloneableOwnerCap` (a leader's capability) | Leader | | Any protocol singleton — the tool registry, agent registry, network auth, leader registry, priority-fee vault, protocol object | **Deployment**, with that object's row opened and scrolled into view | | Anything else | The generic **Object** page | The routing is by type name, which is the kind of rule that fails quietly — an unrecognised type does not error, it falls through to the generic page and the search looks like it worked. The list above is the set that is explicitly handled; if an id you know is a protocol object lands on the generic viewer, that viewer still unwraps its versioned state, so nothing is lost. A typed result card opens first, naming what was found, so you can confirm before navigating.
The Explorer search with a typed result card

Search classifies what you pasted and names what it found before navigating.

### The generic Object and Transaction pages `/explorer/object/` — **Object Overview** (id, Move type, owner, version), **Last Modified By**, and **Transaction History**. For a protocol object it additionally **unwraps the versioned state** and renders its fields with the same decoders the [Deployment](/guides/vision-explorer/deployment.md) page uses, so an agent registry or a task payment reserve reads as its fields, not as `{ id, state }`. If the id belongs to an object that is *wrapped* inside another — the default DAG executor's agent lives inside the agent registry — the page reads it through its owner and links to the parent, instead of declaring it missing. `/explorer/tx/` — **Transaction Overview**, **Balance Changes**, and **Gas Details**, with the protocol events the transaction emitted. Every execution and task page links its transactions here. --- # 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/vision-explorer/search.md?ask=&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.