prompt_block — a rendered, drop-in instruction you can place in an
agent’s prompt so it matches that voice.
Authorization
Your bearer token:
Bearer <token>. See Authentication.Request body
The conversation to analyze.
The messages to analyze, in order. Must contain at least one message.
Optional label for where the transcript came from (e.g. a chat name).
A stable identifier for the message, unique within the transcript.
Who sent the message (a display name or stable id).
The message text.
Optional channel or room the message was sent in.
Optional timestamp for the message.
Optional
id of the message this one replies to. Preserving reply structure
improves the analysis.Request
Response
A ready-to-use, human-readable instruction block describing how to write like
this group. Drop it straight into an agent’s prompt.
The structured profile the
prompt_block is rendered from. Top-level fields
include summary, register (formality, warmth, casing), style (length,
formatting, emoji), lexicon, banned_phrases, address, taboos, humor,
roles, norms, in_jokes, and meta. Read individual fields when you want
finer control than prompt_block gives.200 OK
Errors
| Status | Code | When |
|---|---|---|
400 | VALIDATION_ERROR | The transcript is too large or it could not be analyzed. |
401 | UNAUTHORIZED | The bearer token is missing, invalid, or expired. |
402 | PAYMENT_REQUIRED | Your credit balance can’t cover the request. See Credits and billing. |
403 | forbidden | The credentials are valid but not permitted for this endpoint. |
422 | VALIDATION_ERROR | The body is malformed or messages is empty. |
502 | UPSTREAM_ERROR | A dependency the request relies on was unavailable. Retry. |

