> ## Documentation Index
> Fetch the complete documentation index at: https://quintus.tec.br/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Quintus APIs

> Understand the difference between the Agents API and the Public Chats API.

## Two APIs, two integration scenarios

Quintus exposes two main agent-facing APIs, each designed for a different type of flow.

### Agents

This API is intended for agent sessions or one-off executions in integrations such as N8N, Make, and internal systems.

It uses `X-API-Key` on every request and provides sessions, users, files, and one-shot executions.

### Public chats

This API is intended for public-facing environments such as the chat widget provided by Quintus. For enablement and configuration details, contact support.

Use this API when the conversation happens in end-user interfaces such as:

* a website chat;
* an authenticated portal assistant;
* in-app support on mobile;
* embedded frontend experiences.

It starts a conversation with `X-API-Key` and then continues the session with `session_token`.

<CardGroup cols={2}>
  <Card title="Agents" icon="robot" href="/en/public/api/agents/overview">
    API for agent sessions and one-off executions in backend integrations.
  </Card>

  <Card title="Public chats" icon="globe" href="/en/public/api/public-agents/overview">
    API for public-facing environments such as the Quintus chat widget.
  </Card>
</CardGroup>