> For the complete documentation index, see [llms.txt](https://help.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stockcharts.com/learning-more/policies-and-limitations/no-service-level-guarantees.md).

# No Service Level Guarantees

**We cannot guarantee the availability of our service. There are too many variables that are out of our control for us to make such a guarantee.**

That said, we will work as hard as possible to ensure that our service is up and running whenever you need it. (We also maintain a [Twitter feed](http://twitter.com/StockCharts) where we report service availability issues.)

If you are making second-by-second trading decisions, we strongly recommend that you have a backup quote service available in case you are unable to contact our site for any reason.

If a service outage does occur, we may or may not provide some form of compensation to members. Typically, compensation would be in the form of additional subscription time.


---

# 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://help.stockcharts.com/learning-more/policies-and-limitations/no-service-level-guarantees.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.