Person chat
Request example
/api/v1/chat- Scope
chat- Formats
- JSON · SSE
- Sandbox
- Free fixtures
Body parameters
personobjectrequiredThe subject of the conversation. person.name is required.
messagesMessage[]requiredThe conversation so far. Each message has a role (user or assistant) and content string. At least one message is required.
contextstringOptional extra grounding context (e.g. a prior dossier summary) to steer the answer.
formatenumsse to stream the answer token-by-token, or json for the collected response.
ssejsonDefault: sse
sandboxbooleanReturn deterministic, unmetered fixtures for CI, demos, and parser development.
Default: false
Response
JSON responses preserve the operation result and include request metadata, usage, and collected events. SSE delivers progress and result events as they arrive.
Sources & coverage
Continue a conversation about a subject. Send the running message history and DeepSearch streams a grounded answer plus suggested follow-up questions, drawing on the person's public footprint.
Usage & caching
Chat settles from the model tokens and paid tools the request actually uses.
Examples illustrate the contract. Test request runs the selected deployment; sandbox fixtures are unmetered.