> For the complete documentation index, see [llms.txt](https://docs.aimlapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aimlapi.com/faq.md).

# FAQ

- [How can I work with my API keys?](https://docs.aimlapi.com/faq/how-can-i-work-with-my-api-keys.md)
- [Can I use API in Python?](https://docs.aimlapi.com/faq/can-i-use-api-in-python.md): Quick guide about how to configure Python on different operational systems to use AI/ML API with it.
- [Can I use API in NodeJS?](https://docs.aimlapi.com/faq/can-i-use-api-in-nodejs.md): Quick guide about how to configure NodeJS on different operational systems to use AI/ML API with it.
- [How to use the Free Tier?](https://docs.aimlapi.com/faq/free-tier.md): FAQ section about AI/ML API Free Tier option.
- [Are my requests cropped?](https://docs.aimlapi.com/faq/my-requests-are-cropped.md): Find out why your API requests are being cropped and how to prevent data truncation.
- [Can I call API in the asynchronous mode?](https://docs.aimlapi.com/faq/call-api-in-the-asynchronous-mode.md): Learn how to call the API in asynchronous mode to handle long-running tasks efficiently.
- [OpenAI SDK doesn't work?](https://docs.aimlapi.com/faq/openai-sdk-doesnt-work.md): FAQ section with several possible reasons of the problem with OpenAI SDK.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aimlapi.com/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
