> For the complete documentation index, see [llms.txt](https://boongle-development.gitbook.io/windflow-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boongle-development.gitbook.io/windflow-ai/terms-of-service.md).

# Terms of Service

Please follow our small Terms Of Service when using our API.

1. Using WindFlow AI API for illegal activities is strightly prohibited. Uncensored models abuse is allowed, but normal models abuse is NOT allowed.
2. Selling fake power plan / pro plan for our website to abuse / scam people is strightly unallowed.
3. Leaking paid api keys somewhere is not allowed. Keep your API Key safe, if your API Key got leaked, please **Revoke** it.

You don't have to give us any credits when using it in your own project or whatever and you can also claim it as your own service. That's fine too. You can also sell api access trough our API.


---

# 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://boongle-development.gitbook.io/windflow-ai/terms-of-service.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.