> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/reference/getting-started/introduction.md).
# Introduction
This API allows you to connect to our platform and manage different resources automatically. Instead of performing actions manually—such as creating items or checking information through a web interface—you can do it by sending requests from your application or scripts.
If you’ve never used an API before, don’t worry: the main idea is that you send a request to a specific address (an endpoint), and the platform returns a response in **JSON** format, which is a very easy-to-read text format.
The API is organized into different sections, each dedicated to a type of resource. For example, there may be sections for creating resources, listing the ones you already have, or updating their configuration. Each action is performed using well‑known HTTP methods such as **GET, POST, PUT, PATCH or DELETE**.
To use it securely, you will need a token that identifies you as an authorized user. We also provide tools like pagination, filters, and clear error messages to help you understand what is happening at every step.
This document is an initial guide to help you get familiar with the general structure of the API and start integrating it into your own applications, even if you have no prior experience.
---
# 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.plenit.com/reference/getting-started/introduction.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.