# Web3 Name API & SDK

Streamline digital identity integration with SPACE ID's all-in-one Web3 Name API & SDK, empowering developers with simplicity, scalability, and game-changing potential.\
\
One API & SDK for all has always been one of the main features of SPACE ID to support all web3 dApps. It is ultimately designed to be a unified and streamlined approach that greatly simplifies the integration of web3 services, eliminating the need for developers to work with multiple protocols, saving time and reducing the risk of compatibility issues.\
\
Web3 Name API & SDK includes a suite of features and functionalities designed to facilitate domain name resolution and reverse resolution. This comprehensive SDK is equipped to support various top-level domains (TLDs) like .eth, .bnb, .sol, .arb, and the verified domains that are launched through the SPACE ID Toolkit. Additionally, it dynamically supports new TLDs as they are verified, ensuring seamless integration for domain name resolution and reverse resolution.

For example, suppose you have integrated Web3 Name API / SDK, allowing it to support .bnb domain resolution on BNB Chain. When a new TLD, such as .allen, is launched on SPACE ID and subsequently verified, the SDK will automatically extend its capabilities to include .allen domain name resolution. This process requires no additional upgrades or development costs, streamlining domain management for developers and users.

Notably, the Web3 Name API & SDK also accommodates domain names associated with blockchains outside the EVM, such as .sei, .inj, and .sol.


---

# 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.space.id/developer-guide/web3-name-api-and-sdk.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.