SentientOne Documentation

Everything you need to build, ship, monitor, and govern AI agents on the SentientOne platform — explained one page at a time, in the same language the product uses.

How SentientOne fits together

SentientOne request flow — your app → SentientOne API → agent config → LLM + MCP tools
Your app sends one POST request. SentientOne loads the agent config, runs any MCP tool calls, and returns the AI response.

What SentientOne is

A simple, request-driven agent platform. You build an agent in the dashboard — give it a system prompt, a persona, the tools it can call, and the knowledge it should ground its answers in — then invoke it from any internal app with a single POST /v1/chat. One endpoint, two headers, JSON in / JSON out. That's the whole product surface.

  • Prompt + personaConfigure the system prompt and tone once, version it, and roll back when you need to.
  • Tool callingConnect MCP servers so the agent can look things up in your APIs (orders, products, tickets, anything you expose).
  • KnowledgeUpload documents, drop in Q&A snippets, crawl a website — the agent retrieves the right context on every call.
  • One API callSame call shape from every app — web, mobile, internal tools, cron jobs. Route to a different agent by changing the X-Agent-Id header.

What SentientOne isn't

We're deliberately not in some of the spaces other "agent platforms" live in. Knowing what we don't do helps you pick the right tool for your problem.

  • Not an always-on agentAgents don't sit in the cloud running on their own. They wake up when your app calls them, do their work in a few seconds, and shut down. If you need long-running autonomous workers, that's a different shape of product.
  • No idle billingWe don't charge for time agents sit idle or for requests you don't send. The plan covers a monthly request bucket; if you don't use it, you don't pay for it.
  • You pay the LLM directlyToken cost goes straight to your provider (OpenAI, Anthropic, Gemini, Groq) on your own key. We never mark up tokens or proxy your provider bill — see LLM Keys.
  • Not a workflow orchestratorOne request, one conversation, one reply. We're not a long-running pipeline engine — if you need DAGs of steps that run for hours, pair us with a workflow tool and call us per step.
  • Not a model trainerYour prompts and conversations are never used to train any model. The platform passes data through to the LLM and back — see Security.

The platform at a glance

SentientOne · app.sentientone.ai
Workspace overviewWorkspace: AcmePlan: Pro+ New Agent
Agents5

Configure system prompts, models, knowledge, and tools.

Analytics7d

Usage, cost, latency, and errors across every agent.

TracingLive

Step-by-step execution timeline for any API call.

ChatBotEmbed

Embed any agent as a public widget on your website.

OrganizationPro+

Brand the portal, invite teammates, scope agent access.

REST APIv1

One POST endpoint, two headers, JSON in / JSON out.

5 agents3 LLM keys4,210 requests / mo

Where to start

Build

Observe

Configure

REST API

Platform

Frequently asked

What's the difference between an agent and a chatbot?
An Agent is the configured brain — system prompt, model, tools, knowledge. A ChatBot is a public widget that exposes an agent on your website. The agent does the thinking; the chatbot is how visitors talk to it.
Do I need to bring my own LLM key?
Yes. Save your provider key once in LLM Keys and every agent in your workspace can pick it up from the Use saved key dropdown. You pay the provider directly for tokens; SentientOne charges only for the platform.
Can the same key call multiple agents?
One platform key (X-Api-Key) authenticates your account. Use the X-Agent-Id header to pick which agent runs each request. A single integration can route to as many agents as you need.
Where do I see what a request actually did?
Tracing shows the full step-by-step timeline for any request — LLM call, MCP tool calls, knowledge retrieval, latency per step. Every response carries an X-Trace-Id header you can paste into the filter to find the exact request.
Is my data used to train models?
No. Conversations and prompts are never used to train any model. See Security for the full data-handling picture.
Can I run SentientOne on my own infrastructure?
Yes — on Enterprise. Hosting & Deployment covers cloud, on-premise, hybrid, and air-gapped options.

How to read these docs

Every page is structured the same way: a short intro, an annotated mock of the screen, a widget reference, and a step-by-step how-to. Use the global search (⌘K) to jump between pages, the right-rail TOC to jump within a page, and the prev/next buttons at the bottom to read straight through.