# Guides

End-to-end guides for XOXNO's swap aggregation, transaction relaying, and real-time blockchain data services. These guides cover complete workflows, not individual endpoints — start here before consulting the API reference.

## Guides

| Guide                                                                | Description                                                                                                    |
| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| [System Architecture](/developers/guides/system-architecture.md)     | How arb-algo, mx-relayer, and mx-notifier fit together: protocols, data flows, and operational characteristics |
| [Transaction Lifecycle](/developers/guides/transaction-lifecycle.md) | Complete walkthrough of a swap from quote to on-chain confirmation, including error handling at every step     |
| [Quickstart](/developers/guides/quickstart.md)                       | Get from zero to a working swap integration in under 5 minutes                                                 |
| [Gas Optimization](/developers/guides/gas-optimization.md)           | Use real-time gas statistics to minimize cost and maximize confirmation speed                                  |

## API Reference

For endpoint-level documentation:

* [Aggregator API](/developers/aggregator-api.md) — Quote, pair config, and health endpoints
* [Relayer WebSocket API](/developers/relayer-api.md) — Gas stats, account subscriptions, relaying, broadcasting
* [Notifier](/developers/notifier.md) — Internal blockchain event distribution


---

# 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.xoxno.com/developers/guides.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.