> For the complete documentation index, see [llms.txt](https://docs.metaid.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metaid.io/metaid-app-node/browser.md).

# Browser

{% hint style="info" %}
We have deployed the MAN browser, and the source code has also been open-sourced on Github:\
<https://man.metaid.io/>
{% endhint %}

The MAN indexer includes a built-in MetaID browser that supports querying MetaID-related data.

### Running the Browser

To start the HTTP web service, set the `server` parameter to 1 when running the program:

```bash
./manindexer -server=1
```

The default ports for the service are 80/443. If you need to specify a different port, you can do so in the configuration file under the `web` section.

Once the service is started, access it via `http://127.0.0.1:{port}`.

### Browser Features

#### Search

The search function accepts keywords such as MetaID, PIN Number, and PIN ID. Note that fuzzy search is not supported.

#### PIN

A list of all PINs, displayed in reverse chronological order with pagination. Clicking on a specific PIN provides more details, such as:

[9bc429654d35a11e5dde0136e3466faa03507d7377769743fafa069e38580243i0](https://man.metaid.io/pin/9bc429654d35a11e5dde0136e3466faa03507d7377769743fafa069e38580243i0)

#### MetaID

A list of all MetaIDs, sorted by creation time in descending order. Clicking on a specific MetaID shows the PIN used to create that MetaID.

#### Block

A list of all blocks containing MetaID protocol data, sorted by block height in descending order. Clicking on a block card displays the details of the transactions within that block, such as:

<https://man.metaid.io/block/844453>

#### Mempool

Lists MetaID data in the memory pool, which is automatically deleted after being included in a block.


---

# 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://docs.metaid.io/metaid-app-node/browser.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.