> For the complete documentation index, see [llms.txt](https://brightid.gitbook.io/aura/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brightid.gitbook.io/aura/future-tools/explorer-view.md).

# Aura Graph Explorer

### [Old Aura Explorer](https://explorer.brightid.org/?aura=aura)

{% embed url="<https://explorer.brightid.org/?aura=aura>" %}

### New explorer

The new graph explorer (as yet unreleased) is tailored to Aura's use of roles. It will show the role relationships between participants and the impacts of evaluations.

### Viewing a specific person

On a subject's profile, click "View on Explorer" to view how Aura players have evaluated them.&#x20;

![](/files/ikqZmOtPQUEOL5ASbyDQ)

### Comments

Players can leave comments or ask questions about a person or group of connected people on the graph by placing dots around a region or node with shift-click.  Other players can then respond.

#### Reasons for comments

Players may want to ask how they can make a connection to a region to do more research.  They may want to flag a certain region as suspicious, or ask for more information about it.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://brightid.gitbook.io/aura/future-tools/explorer-view.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.