Authentication

• X-Api-KeyYour platform API key. Starts with sk-so-. Found in Settings → API Key. Authenticates your account.
• X-Agent-IdUUID of the agent to invoke. Found on the Agents page on the agent card or in the agent detail header.
• Content-TypeAlways application/json.

The chat endpoint streams its reply as Server-Sent Events. Use curl -N to disable buffering so each event arrives as it's emitted.

curl -N -X POST https://api.sentientone.ai/v1/chat/stream \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: sk-so-your_api_key_here" \
  -H "X-Agent-Id: a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  -d '{ "message": "Hello!" }'

The response is a stream of data: lines. Concatenate the content of every delta event to build the full answer:

data: {"type":"meta","conversation_id":"...","trace_id":"..."}
data: {"type":"sources","sources":[{"index":0,"id":"...","title":"...","url":"...","source_type":"...","score":0.9,"snippet":"..."}]}
data: {"type":"delta","content":"Hel"}
data: {"type":"delta","content":"lo!"}
data: {"type":"done","conversation_id":"...","trace_id":"..."}

On failure the stream emits an error event instead: data: {"type":"error","code":"...","message":"..."}.

The X-Api-Key is yours and authenticates the call to the platform. The X-Agent-Id picks the configured agent. Different requests can target different agents using the same key — that's how a single integration can route to a Support agent, an HR agent, and an Order Status agent without ever reshuffling credentials.

Never expose X-Api-Key in client-side code, public repos, or browser network requests. Call the SentientOne API from your backend server and proxy responses to your frontend. If a key leaks, rotate it from Settings — the old key is invalidated immediately.