> For the complete documentation index, see [llms.txt](https://ai-docs.fptcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.fptcloud.com/service-level-agreement/1.-terms-of-use.md).

# 1. TERMS OF USE

* **FPT Smart Cloud** and **Client** agree to abide by the terms and conditions of this SLA.&#x20;
* This SLA only applies to **FPT AI Factory** service, and does not apply to other operations support services, including but not limited to: ADSL service, Voice service.&#x20;
* For compliance with the provisions of law, **FPT Smart Cloud** has the right to update and modify this SLA over time. **FPT Smart Cloud** shall provide at least 30 days' notice to the Client for term changes to this SLA.&#x20;
* In the event of a conflict between this SLA and the Contract, this SLA shall prevail, unless such conflict is regulated by the Contract and mutually agreed by both parties.


---

# 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://ai-docs.fptcloud.com/service-level-agreement/1.-terms-of-use.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.
