# Using REST APIs

Checkout REST APIs document at:

{% embed url="<https://api.nad.domains/api-docs>" %}

## Pros & Cons

### ✅ Pro

* **No blockchain tooling needed**: just HTTP requests.
* **Easy integration**: ideal for backends, service scripts, or environments where SDKs or RPC clients aren’t ideal.
* **Rapid prototyping**: fetch name resolution, profiles, etc., via simple endpoints.
* **Language Agnostic**: Works with any tech stack.

### ⚠️ Cons

* **Network latency**: HTTP is slower compared to direct RPC.
* **API stability / rate limiting**: subject to API versioning and limits.
* **Potential Latency**: May not reflect the very latest on-chain state.

**Best for:** Traditional web applications, mobile apps, or scenarios where blockchain interaction complexity isn't warranted.


---

# 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.nad.domains/developers/integrating-into-your-dapps/using-rest-apis.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.