Do I need an SDK to talk to my agent?

No. The session and chat endpoints are plain HTTP with a server-sent event stream as the response, callable from any language with fetch, curl, or an HTTP client. There is no client package for them.

How do I authenticate?

With an Authorization header carrying the end user's own credential, or an X-Api-Key from API keys when there is no signed-in user. Both are described in Application endpoints.

Can I call the chat endpoint straight from the browser?

Only with a signed-in user's own Authorization token, never with an X-Api-Key: that key has full access to every application in your account, so shipping it to the browser exposes your whole account. For a public chat with no signed-in user, put a backend between the browser and Tuix AI Agents and keep the key there.

Why does the chat endpoint answer 404 'Session not found'?

Either x-session-secret is missing or wrong, or the sessionId has expired or never existed, see Request reference. All three answer the same way on purpose, so a request can't be used to guess valid session IDs. The fix is always the same: call the session endpoint again to start a new session.

How long does a session last?

1 hour from creation. After that, its history is gone and its sessionId no longer works; start a new session to continue talking to the agent.

Where do I find my Application ID?

On the application's Application Endpoints tab in the dashboard, alongside the ready-to-use session and chat URLs.

How do I let the agent call my own API?

Generate an MCP server from your API's OpenAPI document, see Generate from OpenAPI. Mark the endpoints you want to expose with x-mcp: true, and once it reaches Deployed the agent can use it on the next message, no redeploy needed.

Can many users talk to the agent at the same time?

Yes. Every conversation has its own sessionId, created independently by calling the session endpoint once per user. Sessions don't share state or queue behind each other.

What shape do error responses come back in?

Always {"message": "..."}, whatever went wrong: an authentication failure, a validation error, or a session that couldn't be found. Branch on the HTTP status code and use message for a human-readable description, see Request reference.

Basics

Getting Started Create an application Prerequisites API keys

Configure Agent

Prompt and initial message Knowledge MCP Servers Role scope Application endpoints

MCP Server

Generate from OpenAPI Connect with agent Authorization Metadata

Reference

Request reference FAQ

FAQ

Common questions about Tuix AI Agents.