> For the complete documentation index, see [llms.txt](https://docs.architect.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.architect.co/algos-book/spreader/spreader-status.md).

# Spreader Status

### SpreaderStatus

| Parameter                | Description                                                                                                                       |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| leg1\_fill\_quantity     | Signed, filled quantity on leg 1                                                                                                  |
| leg2\_fill\_quantity     | Signed, filled quantity on leg 2                                                                                                  |
| implied\_spread\_vwap    | The average filled price of completed spread units so far                                                                         |
| current\_spreader\_phase | [SpreaderPhase](#spreaderphase)                                                                                                   |
| leg1\_quote\_order\_id   | The [QuoteOneSide](https://docs.architect.co/algos-book/quoteoneside.md) order ID for Leg1, if Leg1 has a quote out in the market |
| leg2\_quote\_order\_id   | The [QuoteOneSide](https://docs.architect.co/algos-book/quoteoneside.md) order ID for Leg1, if Leg1 has a quote out in the market |
| spread\_price            | The current spread taking price (the price to cross the implied market)                                                           |

### SpreaderPhase

| Parameter              | Description                                                                                                                                                                   |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **NoBbo**              | Either the bid or the ask does not exist. Usually this means the market is closed, or you caught the algo before it fully subscribed to market data (common in paper trading) |
| **Waiting**            | Algo order is live, but no orders in any of the legs are in the market                                                                                                        |
| **OrdersInMarket**     | Algo order is live, with orders in at least one of the legs live in the market                                                                                                |
| **DoneNotFullyFilled** | Algo order has halted (generally from **MissedTakePolicy.Halt**) but the original spreader quantity is not fully complete                                                     |
| **Done**               | Algo order has completed                                                                                                                                                      |


---

# 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.architect.co/algos-book/spreader/spreader-status.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.
