Stateless chat
Asks CodeAlive’s built-in research agent a question and returns a synthesized, evidence-grounded answer. Each call is stateless: no conversation is stored, so include all relevant prior findings, artifact identifiers, constraints, and scope in question. This is the highest-latency, highest-cost tool — when orchestrating your own agent loop, prefer the direct search and read tools and reserve chat for when a delegated end-to-end answer is explicitly wanted.
Authorizations
API Key authentication using Bearer token. Example: "Authorization: Bearer {apiKey}"
Body
Self-contained question. Tool API v3 chat is stateless; include any prior findings, identifiers, constraints, and assumptions.
Optional success projection. Omit to return both obj and rendered; use json for obj only; use agentic for rendered text only. Repairable errors always return both obj.error and rendered.
json, agentic Repository or workspace names returned by get_data_sources. Omit only when the API key has a single unambiguous scope.
Response
Success envelope. obj is { answer, stateless: true, hint }; rendered is the answer text itself. Repairable failures (missing or invalid arguments, ambiguous or unknown data sources) also return HTTP 200 with obj.error = { code, message, retry, try } and a rendered <tool_error> block; repair the arguments and retry.