> For the complete documentation index, see [llms.txt](https://docs.neurelo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neurelo.com/getting-started/starting-your-neurelo-project/try-your-neurelo-apis.md).
# Try your Neurelo APIs
### Testing Your Project with Neurelo APIs
After setting up your Neurelo project, the next step is to test and experiment with the APIs that have been generated for your project. Here’s how you can proceed:
1. **Accessing the API Playground**:
* Locate the option "API Playground" on your Neurelo Dashboard
* Clicking this option will redirect you to the Environments section of your project and load the API Playground.
2. **Testing REST and GraphQL APIs**:
Within this section, you have the ability to view and interact with your REST and GraphQL APIs.
{% hint style="info" %}
You will need to add your API Key in the "X-API-KEY" header to be able to use your APIs
{% endhint %}
### **Further Actions and Information**:
* For a more comprehensive understanding of all the actions you can perform in this section, refer to the \[[Environments](/environments.md)] documentation page. This documentation will offer detailed guidance on utilizing the full range of features available in your Neurelo project's environment.
---
# 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.neurelo.com/getting-started/starting-your-neurelo-project/try-your-neurelo-apis.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.