> For the complete documentation index, see [llms.txt](https://sdk.chorus.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.chorus.one/reward-reporting/reward-reporting.md).

# Overview

Programmatic access to staking rewards data across supported networks.

The Reward Reporting APIs provide programmatic access to staking rewards data for institutional clients and partners. Use them to retrieve daily and epoch reward earnings, validator and pool performance, and exportable data for reconciliation and compliance.

Production base URL: `https://rewards-api.chorus.one`.

## Reward types

Reward Reporting is available at two levels:

| Type                | What it returns                                                                                            |
| ------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Network rewards** | Onchain staking reward data: the rewards generated on the network, such as daily or epoch reward earnings. |
| **Account rewards** | Onchain reward data supplemented with commission and account-specific commercial parameters.               |

## Supported networks

| Network         | Reward type     | Coverage                                        |
| --------------- | --------------- | ----------------------------------------------- |
| **Solana**      | Network rewards | Vote-account and staking-authority rewards      |
| **Ethereum**    | Network rewards | Vault rewards (powered by StakeWise V3)         |
| **TON**         | Network rewards | Pool and nominator rewards                      |
| **NEAR**        | Network rewards | Delegator epoch rewards, net of pool commission |
| **dYdX**        | Account rewards | Delegator rewards and validator commissions     |
| **Hyperliquid** | Account rewards | Delegator rewards and validator commissions     |
| **Aleo**        | Account rewards | Delegator rewards and validator commissions     |

## Authentication

All requests require an API key passed in the `X-API-KEY` header. Your key is automatically scoped to the wallets mapped to your account.

To generate and manage keys, see [Rewards Dashboard API Keys](/rewards-dashboard-api-keys.md).

## Next steps

* [Network Rewards](/reward-reporting/reward-reporting/network-rewards.md): onchain reward data for Solana, Ethereum, TON, and NEAR.
* [Account Rewards](/reward-reporting/reward-reporting/account-rewards.md): rewards plus commission and account data for dYdX, Hyperliquid, and Aleo.


---

# 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://sdk.chorus.one/reward-reporting/reward-reporting.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.