# Quickstart Guide

## Welcome

Welcome to the Nexus API documents, where you can find all the documentation you need. If the link you currently have does not work, you can always go to <https://www.dotswap.app/> to get the latest documentation address.

## Examples

Every module of this documentation will provide viable examples for Nexus's current process flow. Example execution methods include:

* **curl**, which you can copy to any place that can execute curl to see the results, like the terminal in Mac.
* **Test parameters**, which you can directly copy into the provided apifox documentation for online debugging. (Clicking on any document's interface will take you to the current interface's apifox documentation.)

## Global

* Test environment API prefix: <https://api-testnet4.dotswap.app>
* Production environment API prefix: <https://api.dotswap.app>

## Notes

1. The documentation will provide **TypeScript interfaces**. If there is a discrepancy with the Apifox parameters, the TypeScript parameters in this document will prevail.
2. The notes in each document should cover most of the problems you might encounter, please do not ignore them.
3. On Nexus, all interface BTC communication units are in **satoshis** (0.00000001 BTC). That is, **the backend returns satoshis and also receives in satoshis**.
4. The value of `fee_rate` must be greater than or equal to the priority level in the BTC [Mempool](https://mempool.space/). Access Mempool's fee rate interface 👉 [here](https://mempool.space/api/v1/fees/recommended)

*All examples provided in this document are for the test environment.*


---

# 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.on.nexus/dotswap/developers/introduction-and-quickstart/quickstart-guide.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.