> For the complete documentation index, see [llms.txt](https://docs.stonksnipebot.best/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stonksnipebot.best/deployment-and-operations/runtime-status-and-readiness.md).

# Runtime Status and Readiness

### Monitoring status

Use `/speed` to inspect monitoring speed. Use `/status` for the service state. Duplicate observations from Validation Cloud and ArrowRPC are deduplicated.

The service monitors Robinhood Chain over WSS and HTTPS. Feed availability does not prove that a trade route is available.

### Trading readiness

Use `/trading_status` before enabling live strategies. A ready execution requires a verified route and pinned codehash.

It also requires a fee limit, quote, slippage limit, `eth_call` simulation, gas estimate, sufficient ETH balance, signing, broadcast, and receipt confirmation.

### Learning gate

Live execution begins with one designated learning wallet. Confirmed learning-wallet buys and sells can release the trading gate for all custody wallets.

Fee collection follows the same staged approach. It expands after the first learning-wallet fee collection confirms on-chain.

{% hint style="warning" %}
A running deployment is not proof of trading readiness. No route means no transaction.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stonksnipebot.best/deployment-and-operations/runtime-status-and-readiness.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.