# Indexer API

The **Indexer API** is a powerful tool designed to provide seamless access to blockchain data, enabling developers to interact with collections, pools, positions, transactions, and more. This API allows you to:

* **Manage Collections**: Retrieve and search for collections (runes) with advanced filtering and sorting options.
* **Access Pool Data**: Obtain detailed information about liquidity pools, including statistics and historical data.
* **Monitor Positions**: Fetch user positions, estimated yields, and pool statistics.
* **Query Transactions**: Access transaction histories for specific pools or users, with support for filtering by date, type, and tokens.
* **Obtain Market Data**: Retrieve OHLC (Open, High, Low, Close) data for asset pairs to support trading and analysis applications.

The Indexer API stands out for its robustness and flexibility, providing comprehensive endpoints that cater to a wide range of blockchain data needs. Its powerful querying capabilities make it an indispensable tool for developers building applications in the decentralized finance (DeFi) space.

To make integration even more straightforward, we offer:

* [**Typescript SDK**](https://www.npmjs.com/package/@saturnbtcio/indexer-api-sdk): A fully-featured SDK, allowing for easy and type-safe interactions with the API.
* [**Swagger Documentation**](https://indexer.staging.saturnbtc.io/swagger): An OpenAPI specification is available, providing detailed information about each endpoint, request, and response format.


---

# 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.saturnbtc.io/builders/saturn-api/indexer-api.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.
