DocsPlatformOverview

The platform at a glance.

Essarion is one platform composed of three systems — a citation-grade research engine, a project-scoped agent workspace, and a programmatic API that ties them together. This page is the orientation. Read it once, then jump into whichever surface you actually need.

§ 01What is Essarion

Most "AI" products are a single chat box wrapped around a single model. Essarion is built differently. It is an operating workspace for serious work — research, analysis, document review, code, diligence — with the runtime, governance, and observability that platform teams have to own.

The platform exposes that runtime in three ways. You can sit inside the workspace as a user. You can let an end-user sit inside it as your customer. Or you can call the engine directly from your own product through the API.

NoteIf you only read one section of these docs, read Core concepts next. Almost every page that follows assumes those terms.

§ 02Three systems

The platform is one product surface; underneath it is three engines that share state, identity, and policy.

ResearchAnything.ai

A research agent that takes a question and returns a citation-ready answer. It plans sub-queries, searches the open web, scrapes and screens the results, scores sources for credibility and relevance, performs deep analysis on the survivors, and synthesizes a final report with formal citations in any of MLA, APA, Chicago, IEEE, Harvard, or BibTeX. Every step is persisted; every claim is traceable to a source. → Read more.

Essarion Agents

A project-centric AI workspace. Agents read and write files in a per-project drive, run real terminal commands in an isolated PTY, drive a real cloud browser through Stagehand, and produce auditable artifacts. They can spawn subagents to parallelize work, follow domain-specific skill packs and policy bundles, and run pre-built jobs for accountancy, contract review, executive briefs, and more. → Read more.

Platform API

A small, documented HTTP surface for the same engine that powers the workspace. Submit a research query, subscribe to a stream of events, fetch the timeline of a run, manage keys, view usage. Build with Essarion behind your own product. → Read more.

§ 03How they fit together

The three systems are not silos. They share four things:

For the wiring diagram and component-level architecture, see Architecture.

§ 04Who is it for

Essarion is built for teams that have to ship the answer — not a transcript of a chat. Four audiences in particular:

§ 05How to read these docs

The sidebar is grouped by product. Within each product, pages run in roughly the order you'd actually need them — overview first, then quickstart, then deeper reference.

§ 06Conventions used in these docs

A few signals reappear across every page.

Endpoint blocks

API endpoints look like this:

POST/api/v1/query

The verb is colored, the path is verbatim. Required auth and parameters are listed in a table directly below.

Code blocks

Inline code looks like esk_xxxx. Multi-line examples are labeled with the language they're in.

curl
curl https://api.essarion.com/api/v1/query \
  -H "Authorization: Bearer $ESSARION_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "How does the platform compose?"}'

Call-outs

NoteThings you'll want to know before reading further.
TipThings that will save you time once you do.
CautionThings that will bite you if you skip them.

§ 07Where to go next

Pick the path that matches what you're trying to do.