> For the complete documentation index, see [llms.txt](https://docs.stakingrewards.com/verified-provider-program/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakingrewards.com/verified-provider-program/verification-methodology/sr-rating/verification-criteria/business-operations.md).
# Business Operations
We assess, among other things, the legitimacy of a provider's business, the delegator protection, and the sustainability of their services in a fast-moving environment like crypto. In assessing them, we especially emphasize their business practices, and the veracity of the information they provide. We see this as the cornerstone of a truthful relationship between delegator and validator.
Liability
The crypto market is continuously in a changing environment. For this reason, in this section, we would like to see how the Provider deals with different situations:
* Offering of slashing protection
* Sending funds to the Provider’s validator address instead of delegating
* Strategies for market downturns and alternative strategies
Accountability
In this section, it is asked how long the Provider is operating the services. The longer this is the case, the higher the assumption that there is a long-term interest in continuing the services.
Compliance
Regulatory security and the legitimacy of the Provider’s service are the cornerstones of a trusted relationship between delegator and validator.
In this section, the following aspects are considered:
* The legal jurisdiction under which the operations fall
* Whether the Provider restricts certain jurisdictions in the services
---
# 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.stakingrewards.com/verified-provider-program/verification-methodology/sr-rating/verification-criteria/business-operations.md?ask=&goal=
```
`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.