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

# Talus Vision Explorer

### Talus Vision Explorer

{% hint style="info" %}
**Audience:** Anyone inspecting a hosted Nexus deployment — builders following their own runs and users checking an agent, tool, or public network record before trusting it.

**Goal:** Know which Explorer window answers which question, and the conventions that make its numbers trustworthy.
{% endhint %}

The Talus Vision <https://vision.talus.network> is a public-read surface and home view: all nexus related onchain objects or transactions becomes visible here.

<figure><picture><source srcset="/files/mdUABjJ3INiFtk3KISg4" media="(prefers-color-scheme: dark)"><img src="https://2322144477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlV9L0m4FfiDv8fzxk6cT%2Fuploads%2Fgit-blob-71fa2abc8f28cb3806633eb359b9c845137349fc%2Ff24-vision-explorer-light.svg?alt=media" alt="Vision Explorer reads deployment and chain state"></picture><figcaption></figcaption></figure>

The feature map follows the durable state boundary: Explorer pages are read views over Agents, Tools, DAGs, Tasks, Occurrences, Executions, payments, leaders, and deployment metadata. A loading, unavailable, or unsupported-network state is different from an empty list, and every feature page below names that distinction.

<figure><img src="https://2322144477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlV9L0m4FfiDv8fzxk6cT%2Fuploads%2Fgit-blob-6b32bae826c2f331b4be7f2a3c35770a6ca3e6a1%2Fnexus-explorer-testnet-rc7.png?alt=media" alt="Talus Vision Explorer captured on Testnet with agents, registered skills, and recent activity"><figcaption><p>Explorer evidence retained from the Testnet snapshot. The captured network state is illustrative; verify a live deployment through its selected network and deployment document.</p></figcaption></figure>

### Which window answers what

| You want to know                                                              | Open                                                                              |
| ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| The network at a glance, or one address's whole footprint                     | [Home, Dashboard, and Profile](/guides/vision-explorer/home-dashboard-profile.md) |
| What is this agent, what can it do, who pays for its runs                     | [Checking agents](/guides/vision-explorer/checking-agents.md)                     |
| What does this published workflow actually do, which tools does it call       | [Checking workflows](/guides/vision-explorer/checking-workflows.md)               |
| What does this tool cost, what does it expect, is it trustworthy              | [Checking tools](/guides/vision-explorer/checking-tools.md)                       |
| Did my run happen, where is it stuck, what did it produce, what did it cost   | [Inspecting tasks and executions](/guides/vision-explorer/inspecting-runs.md)     |
| Who dispatches work, what is staked behind them                               | [Leaders](/guides/vision-explorer/leaders.md)                                     |
| Which package and object ids is this app talking to, and does the chain agree | [Deployment](/guides/vision-explorer/deployment.md)                               |
| I have an id / address / digest / FQN and want its page                       | [Search](/guides/vision-explorer/search.md)                                       |

#### Layout

Destinations are grouped the way the protocol's own packages split the domain:

| Group        | Destinations                  |
| ------------ | ----------------------------- |
| **Entities** | Agents · Tools · Workflows    |
| **Activity** | Tasks · Executions · Payments |
| **Network**  | Leaders · Deployment          |

Beside the groups sit two icon buttons — the **Dashboard** and your own **Profile** — and the **search field**, on every Explorer route. There is no Skills tab on purpose: a skill is one row of one agent's table, reachable from that agent's page.

<figure><img src="https://2322144477-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlV9L0m4FfiDv8fzxk6cT%2Fuploads%2Fgit-blob-bb7ce507f6498d49a34558f0f1d24899dd4d12b4%2Fexplorer-nav.png?alt=media" alt="The Explorer navigation bar with its three grouped menus and search field"><figcaption><p>The Explorer's navigation: Entities, Activity, and Network, plus the Dashboard, your profile, and the search field.</p></figcaption></figure>

#### How every list behaves

* **Search field, facet chips, one sort menu.** Facets have no "All" button: no selection means unfiltered, and clicking the active chip clears it. Chips carry the same icon as the row badge they filter.
* **Two kinds of list.** Agents, Workflows, Tasks, Executions, and Payments page as you scroll (**Scroll down for more**). **Tools** and **Leaders** are enumerated in full and filtered client-side, so in those two "no matches" means the registry holds nothing matching — not that you have not scrolled far enough.
* **Rows open detail pages**; every id, address, and FQN is copyable, and creator addresses link to that address's profile.
* **A detail page that cannot find its object says so** and counts down to the list — except for wrapped protocol objects, which it resolves through their owner first (see [Deployment](/guides/vision-explorer/deployment.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/guides/vision-explorer.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.