> For the complete documentation index, see [llms.txt](https://developer.erudus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.erudus.com/getting-started/quickstart-1.md).
# Authentication
### Authentication with API Tokens
To use the Erudus API each request will need to be authenticated using an API Token.
API Tokens are associated with a user of Erudus, and that user must have sufficient permissions in the system for the desired actions to be performed.
Each user is able to create multiple API Tokens. It is recommended that separate tokens be created for different integrations and applications so that they can be managed and controlled independently.
### Creating an API Token
Visit the API portal and select Manage Tokens. Give your new token a name and select appropraite permissions you wish to give this token.
Creating an APi Token in the API Portal
You will be presented with a popup window revealing your new token. Copy and save securely.
### Authenticating Requests
Most API endpoints require an access token to be supplied in the Authorization header. Use the API Token provided in the header as follows:
```
Authorization: Bearer kYwxZ6LKTBrJXtHdThUnq9zKyHa1nteL9cOtsxL45591fd7d
```
---
# 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://developer.erudus.com/getting-started/quickstart-1.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.