# API Reference

Dive into the specifics of each API endpoint by checking out our complete documentation.

## Pets

All the methods associated with `CRUD`ing some pets. Which isn't as weird as it sounds:

{% content-ref url="api-reference/request-to-send" %}
[request-to-send](https://mlayer.gitbook.io/validator-node-api-doc/reference/api-reference/request-to-send)
{% endcontent-ref %}

## Users

Everything related to users:

{% content-ref url="api-reference/approval-to-send" %}
[approval-to-send](https://mlayer.gitbook.io/validator-node-api-doc/reference/api-reference/approval-to-send)
{% endcontent-ref %}

{% hint style="info" %}
**Good to know:** Using the 'Page Link' block lets you link directly to a page. If this page's name, URL or parent location changes, the reference will be kept up to date. You can also mention a page – like [request-to-send](https://mlayer.gitbook.io/validator-node-api-doc/reference/api-reference/request-to-send "mention") – if you don't want a block-level link.
{% endhint %}


---

# 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://mlayer.gitbook.io/validator-node-api-doc/reference/api-reference.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.