> For the complete documentation index, see [llms.txt](https://docs.souless.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.souless.fun/developers/indexer.md).

# Indexer and data

The indexer reads finalized Arc events, normalizes atomic values, and stores projections for markets, swaps, balances, staking, governance, rewards, and public activity.

## Source hierarchy

1. Contract storage and finalized logs are canonical for settlement, custody, and claims.
2. The published network reference identifies the active contracts.
3. PostgreSQL projections provide search, charts, feeds, and historical reconstruction.
4. API-derived metrics and classifiers provide interpretations such as P\&L, narrative, or reputation.

Submitted transaction state is provisional until independently confirmed. A missing indexer update does not undo a chain transaction. Reconciliation jobs should resume from durable block cursors, handle removed/unfinalized observations, and make event ingestion idempotent.

Historical views can be reconstructed from registered launches, transfers, swaps, fee credits, stake checkpoints, governance events, epoch roots, and claims. Derived records should include source block, transaction, calculation version, and update time.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.souless.fun/developers/indexer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.