> For the complete documentation index, see [llms.txt](https://docs.yad.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yad.finance/integration-guides/cross-chain-swaps-api/getting-started.md).

# Getting started

1. Read this documentation.
2. Try out YAD API using [Swagger](https://api.yetanotherdefi.com/swagger/index.html) or request examples we provided in this documentation. 
3. For requests use API url: `https://api.yad.finance`.
4. If you have any questions about partnership with us, feel free to drop a message at: <partners@yad.finance>

### API key management

1. Kindly note that without an API access key, the number of requests per second is limited, it is suitable for testing and development, but not for production capacity.
2. To obtain the key, please get in touch with <partners@yad.finance>.
3. The given key must be added to the header of each request, parameter {"X-API-Key": "\<key>"}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.yad.finance/integration-guides/cross-chain-swaps-api/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.