> For the complete documentation index, see [llms.txt](https://www.aevo.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.aevo.xyz/docs/api-reference/urls/private-api/getbuildermarkets.md).

# GET /builder/markets

Return builder-attributed market totals. Send either period=24h|7d|30d|90d or a custom start\_time/end\_time range up to 180 days. When neither limit nor offset is supplied, all markets are returned.

`GET https://api.aevo.xyz/builder/markets`

> **Authentication required.** Include your `AEVO-KEY` and `AEVO-SECRET` headers. See [Authentication](/docs/api-reference/urls/authentication.md).

## Query Parameters

| Field        | Type    | Required | Description                                                                                                                              |
| ------------ | ------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `period`     | string  | No       | Builder analytics period. Use this or `start_time` and `end_time`, not both. Example: `24h`                                              |
| `start_time` | integer | No       | Window start, Unix nanoseconds. Use with `end_time`, or use `period`. Example: `1672531200000000000`                                     |
| `end_time`   | integer | No       | Window end, Unix nanoseconds. Defaults to now. Example: `1675036800000000000`                                                            |
| `limit`      | integer | No       | Rows per page. Defaults to `50`, maximum `200`. On `/builder/markets`, omit both `limit` and `offset` to get every market. Example: `10` |
| `offset`     | integer | No       | Rows to skip, for numbered pages (`ceil(count / limit)` pages). Use this or `cursor`, not both. Example: `10`                            |

## Example Request

```bash
curl --request GET \
     --url https://api.aevo.xyz/builder/markets \
     --header 'accept: application/json' \
     --header 'AEVO-KEY: <your-api-key>' \
     --header 'AEVO-SECRET: <your-api-secret>'
```

## Responses

**`200`** — Builder market statistics.

| Field     | Type           | Required | Description                                                      |
| --------- | -------------- | -------- | ---------------------------------------------------------------- |
| `markets` | array\[object] | No       |                                                                  |
| `count`   | string         | Yes      | Total rows matching the filters, before pagination. Example: `5` |

`markets` items:

| Field          | Type    | Required | Description                                                                              |
| -------------- | ------- | -------- | ---------------------------------------------------------------------------------------- |
| `instrument`   | string  | Yes      | Instrument name. Example: `ETH-PERP`                                                     |
| `volume`       | string  | Yes      | Volume in USDC terms. Example: `12.23`                                                   |
| `fees`         | string  | Yes      | Builder fees in USDC. Example: `12.23`                                                   |
| `fills`        | integer | Yes      | Number of builder fills. Example: `12`                                                   |
| `maker_volume` | string  | Yes      | Attributed USDC volume where the builder-attributed order was maker-side. Example: `100` |
| `taker_volume` | string  | Yes      | Attributed USDC volume where the builder-attributed order was taker-side. Example: `250` |

**`400`** — Bad request.

| Field   | Type   | Required | Description                                     |
| ------- | ------ | -------- | ----------------------------------------------- |
| `error` | string | Yes      | Error message. Example: `ERR_MALFORMED_REQUEST` |

**`401`** — Unauthorized.

| Field   | Type   | Required | Description                            |
| ------- | ------ | -------- | -------------------------------------- |
| `error` | string | Yes      | Error message. Example: `UNAUTHORIZED` |

**`429`** — Rate limit exceeded.

| Field   | Type   | Required | Description                                   |
| ------- | ------ | -------- | --------------------------------------------- |
| `error` | string | Yes      | Error message. Example: `RATE_LIMIT_EXCEEDED` |

**`500`** — Internal server error.

| Field   | Type   | Required | Description                              |
| ------- | ------ | -------- | ---------------------------------------- |
| `error` | string | Yes      | Error message. Example: `INTERNAL_ERROR` |


---

# 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://www.aevo.xyz/docs/api-reference/urls/private-api/getbuildermarkets.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.