> For the complete documentation index, see [llms.txt](https://faq.carbondefi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.carbondefi.xyz/mechanics/order-execution/100-fill-estimation.md).

# 100% Fill Estimation

When creating a new strategy or editing an existing one, a value called "100% filled estimation" is exposed for ease of use. 

### Goal of estimation

The 100% filled estimation is an indication to makers on the amount of tokens the strategy will hold, should the entire budget be used. Once the order(s) details are provided, the buy or sell average price is identified and multiplied by the entire budget.

### Calculation

#### Price aspect

1. Limit - when entering a limit price, the average execution price is identical to the indicated price.
2. Range - when entering price range, the cost basis for the specified range is equal to the geometric mean of the highest and lowest price boundaries of the indicated range.

$$
GeometricMean =\sqrt{(minPrice)\*(maxPrice)}
$$

#### Budget aspect

Budget indicates the amount of tokens allocated to each order. This is a base value that will be used against the indicated price mentioned above.

#### 100% fill calculation

Using the values from [`Price`](#price-aspect) \* [`Budget`](#budget-aspect) results in the estimated 100% fill value.

### Notice

As orders within a recurring strategy are traded against and refilled, 100% fill estimation results may change.


---

# 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://faq.carbondefi.xyz/mechanics/order-execution/100-fill-estimation.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.