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

# Overview

The Helvia.ai Agents Platform exposes REST APIs through multiple services. Each service handles a specific domain of the platform's functionality.

{% hint style="warning" %}
Not all API services are listed here yet. This section is actively maintained — check back later for additional services.
{% endhint %}

### Services

| Service               | Description                                                                                                                                                  |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **hbf-bot**           | Chatbot executor — runs agent configurations in real-time chat channels (Web, Viber, Messenger, Slack, Teams). No OpenAPI spec.                              |
| **hbf-doc-ingestion** | Document processing — ingests documents (PDF, DOCX, PPTX, HTML, MD, TXT), converts to Markdown, segments into semantic chunks, and optionally tags via LLMs. |

### Common Patterns

All API services follow these conventions:

* **Content-Type**: `application/json` for request and response bodies
* **Error responses**: Standard HTTP status codes with JSON error bodies
* **CORS**: Enabled for all origins in local development


---

# 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.helvia.ai/api/overview.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.