Create chat

Sends one message in a thread (a new thread when thread is absent).

POST /v1/studio/chat

Studio → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/studio/chat`
Method	`POST`
Operation	`post_studio_chat`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Sends one message in a thread (a new thread when thread is absent). The assistant answers in text and, when the message asks for something to be made, plans it as runs and starts them; each is exactly the run POST /v1/studio/runs would start, checked and paid for the same way.

Answers text/event-stream: thread {thread} first; delta {text} as the answer is written; run {seq, run} for each run the turn started (follow it on its own events); error (a problem document) when a planned run could not start — a wallet that cannot cover it is status 402 — and the turn goes on; done {thread, message, runs} last, with the stored message. 402 before the stream when the wallet cannot pay for the turn itself.

Request

5 fields, body application/json.

Field	In	Type	Required
`assets`	body	string[]	—
`brand`	body	string	—
`message`	body	string	—
`model`	body	string	—
`thread`	body	string	—

Response

Status	Body	Meaning
`2XX`	string	Success

2XX body — 1 field.

Field	In	Type	Always	Description
`(body)`	body	string (binary)	yes

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo studio chat

.ts

.py

.go

.rs

.java

import { Configuration, StudioApi } from 'hanzoai';

const api = new StudioApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postStudioChat({ assets: ["<assets>"], brand: "<brand>" });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import StudioApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = StudioApi(client).post_studio_chat(assets=["<assets>"], brand="<brand>")

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.StudioAPI.PostStudioChat(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, studio_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = studio_api::post_studio_chat(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.StudioApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new StudioApi(client).postStudioChat();

curl -X POST https://api.hanzo.ai/v1/studio/chat \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "assets": [
         "<assets>"
       ],
       "brand": "<brand>"
     }'

MCP reaches studio through the studio tool, which names its 32 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_studio_brands"
         }
       }
     }'

Studio API · All Hanzo APIs · Interactive reference

Was this page useful?

Broken link or missing step? Drop it in #docs on Discord or open a PR.

PreviousCreate brands NextCreate documents