> 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/public-api/getbuilderconfig.md).

# GET /builder-config

Returns the protocol builder configuration. max\_fee\_rate\_perps is null until Aevo sets it, min\_create\_balance is null while self-service builder registration is disabled, and option builder fees are disabled until max\_fee\_rate\_options and option\_premium\_cap are both set.

`GET https://api.aevo.xyz/builder-config`

## Example Request

```bash
curl --request GET \
     --url https://api.aevo.xyz/builder-config \
     --header 'accept: application/json'
```

## Responses

**`200`** — Protocol builder configuration.

| Field                  | Type   | Required | Description                                                                                                                                                                                           |
| ---------------------- | ------ | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `max_fee_rate_perps`   | string | Yes      | Protocol maximum builder fee rate for perpetuals as a decimal fraction (0.0005 = 5 bps), or null while unset. A builder\_fee\_rate or approval max\_fee\_rate above it is rejected. Example: `0.0005` |
| `min_create_balance`   | string | Yes      | Minimum human-readable 6-decimal USDC balance required for self-service builder registration, or null while disabled. Example: `100`                                                                  |
| `max_fee_rate_options` | string | Yes      | Protocol maximum builder fee rate for options as a decimal fraction (0.0003 = 3 bps), or null while option builder fees are disabled. Example: `0.0003`                                               |
| `option_premium_cap`   | string | Yes      | Protocol cap on option builder fees as a fraction of premium (0.05 = 5%), or null while option builder fees are disabled. Example: `0.05`                                                             |

**`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/public-api/getbuilderconfig.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.