# Host

## \<path>

The path where the PIN is located. There are three modes to represent `path` as follows:

* Starts with "/": Locates the PIN to be created through the path, e.g., `/protocols/simplebuzz`.
* Starts with "#": Locates the PIN through the PINNumber.
* Starts with "@": Locates the PIN through the PINID.

This is a required option.

## host

```json
**<**path> {host}:{path}
```

In `<path>`, `host` can be an address or a MetaName, for example:

Address: `1PKZnf7DxP69TFTHyzPc5KBidph6yuPKyG`,

```json
1PKZnf7DxP69TFTHyzPc5KBidph6yuPKyG:/protocols/simplebuzz
```

When `host` is included in `<path>`, it declares the source of the data, understood as the host header. This is optional.

If `host` is a MetaName, it must not exceed 32 characters, e.g., MetaName: `alice.metaid`

```json
alice.metaid:/protocols/simplebuzz
```


---

# Agent Instructions: 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:

```
GET https://docs.metaid.io/metaid-specification/host.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.