Overview

The Agent Chat API forwards user messages to a live Gizzi Runtime session and streams the runtime’s event bus back to the caller. The chatId is the platform agent session id created through the agent-sessions flow; the platform simply proxies the payload, preserving provider, model, harness, and system prompt overrides.
This namespace is served by the Allternit API data-plane node (http://127.0.0.1:8013 on the same machine, or your paired or provisioned node). The hosted Cloud API at https://api.allternit.com does not route it; it relays only agent sessions, canvases, office and beta research/sessions. See Cloud API.

Base URL

Authentication

All requests require a valid bearer token in the Authorization header. See Authentication for details.

Endpoints

Send a chat message

Request body

Response

Returns a server-sent event stream from Gizzi Runtime. Each event is a JSON payload on the event bus, for example:

Resume cursor

Frames after a turn’s first trace entry carry an SSE id: the session-trace sequence. Keep the last one and send it as resume.cursor to pick up a dropped stream without duplicating text.

Generated files

A file the model made (an image, deck or document — for example from a connected subscription) arrives after the reply text as an artifact frame:
kind is one of image, audio, video, html, slides, sheet, document. url is a data URL, or the forwarder download URL for files over 24 MB. Reloaded chat history keeps the file part’s id, mime and source, so the same card can be rebuilt.

Chat action

Response

Error codes