Skip to main content
Every Chattler agent can be reached over HTTPS with an API key. A request through the API runs the same runtime as Telegram, WhatsApp or the chat page: the agent’s system prompt, knowledge base, tools and dialog history all apply, and replies are paid for from the owner’s balance in the same way.

​
What the API does

Chat

Send one user message and get the agent’s reply, with token usage and the amount charged.

Stream

Same request, but the reply arrives token by token as server-sent events.

Conversations

List the conversations your key has had and page through their messages.

Quickstart

First reply in five minutes with curl, Python or Node.

​
The basics

A key belongs to exactly one agent. Its permission is either read-only (list conversations and read messages) or full (also chat).

​
Endpoints

​
How conversations work

You do not create conversations. Each chat request names an external_user_id, the stable id of the end user on your side. Every message from the same external user through the same key continues the same conversation; a different key, even for the same agent, has its own separate history. See Conversations.
This release is text only: a message is a string, and attachments are not accepted. Every response carries an X-Request-ID header; quote it when you report a problem.