# REST API

#### Base URL

<pre><code><strong>https://api.tagzz.xyz/
</strong></code></pre>

These APIs are designed to help protocols seamlessly integrate **Tagzz**, your omnichain naming service, within their platforms. The core functionality provided by these APIs is to resolve blockchain addresses into human-readable **domain** and **subdomain** names, and vice versa, allowing protocols to better identify and interact with users through Tagzz domains.

#### Key Functions

* **Single Address or Domain Resolution:** This API allows protocols to resolve a single address into its associated **domain** and **subdomain**. Conversely, it can also resolve a domain and subdomain combination into the associated **address**. This simplifies how protocols identify and display user information without needing to handle long and complex addresses.
* **Bulk Address Resolution:** This API provides the ability to resolve **multiple addresses** in one go, returning the associated **domain** and **subdomain** names. This is particularly useful for protocols needing to handle large sets of user data at once, ensuring efficient domain lookups for a list of addresses.

#### Benefits

• **Simplified User Identification:** Instead of using cryptic addresses, protocols can present users with friendly, readable domain names.

• **Enhanced UX:** Resolving addresses to domains makes interacting with the blockchain more intuitive and user-friendly for external platforms.

• **Scalability:** With the bulk resolution API, platforms can efficiently resolve multiple addresses, improving performance for high-volume operations.


---

# 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://tagzz.gitbook.io/tagzz-your-omnichain-identity/integration-guide/rest-api.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.