# Build with dotHYPE

#### **Whether you're building a wallet, dashboard, or on-chain application, integrating .hype domains helps your users move from raw addresses to structured, readable identity.**

Our resolver is fully on-chain, ENS-compatible, and designed without centralized gatekeepers so you can plug-in with confidence. Everything is modular and upgrade-ready, giving us a stable foundation today and flexibility for tomorrow.

### What You Can Do

* **Resolve Names to Addresses**
* **Read On-chain Text Records** (e.g. Twitter, avatar)
* **Support Reverse Resolution**
* **Query Ownership via ERC721**

### Start Integrating

**→ Resolver Reference**\
Includes ABI, contract address, and example calls (`addr()`, `text()`, `name()`).

**→ Integration Examples (Coming Soon)**\
Code snippets for Ethers.js / Web3.js / React environments.

### SDK (Coming Soon)

Our JS/TS SDK will simplify:

* Name availability + resolution
* Minting hooks
* React-ready UI components

Ready to build with dotHYPE? → [Get Started with the Resolver](/integrating-.hype/build-with-dothype/how-to-get-.hype-integrated-in-your-dapp.md)


---

# 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.dothype.io/integrating-.hype/build-with-dothype.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.