QuoxCORE components · interfaces

Don’t build your own control room.

Five doors into one governed platform. Build them yourself and you maintain five auth paths, five permission checks and five ways to be wrong.

See what ships Try the live demo

Included in QuoxCOREFree, self-hosted, nothing to buy.

Build it yourself and you are signing up for

A dashboard the whole platform fits ina capability your team cannot see is a capability that does not exist
A CLI with real paritysame auth, same permissions, same receipts as the UI, or automation lies
A registry for every tool agents touchregistration, scoping and receipts, nothing ad hoc
An API that fails closeddeny by default on every route, not just the documented ones

Or install QuoxCORE. All of it is already there.

In plain words

What it is, where it lives, when to reach for it

What is it: The doors into QuoxCORE: the dashboard, the chat, the CLI and TUI, the MCP server and the REST API.
Where do I use it: In your browser, your terminal and your model clients; every door opens onto the same governed platform.
When would I use it: Whenever you or your agents need to see, steer or script what the platform is doing.
How do I use it: Open the dashboard, or run quox in a terminal; quox open deep-links from one to the other.

QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE

dashboard

The whole platform, one screen at a time.

Chat, agents, workflows, approvals, evidence, fleet, vault: everything the platform does is visible and steerable in the browser. Chat is its own front door too, with a dedicated page in the family below.

How do I use itquox openDashboard: everywheredeep-links a quox:// URI from your terminal straight into the dashboard view.

A division dashboard in QuoxCORE: teams, agents and activity for one part of the organisation

tool registry

Every tool, on the record.

Anything an agent can touch is a registry entry: created or installed from the catalog, scoped by risk, and receipted on every call. Hosted MCP servers join the same registry as your own tools, under the same rules.

How do I use itquox tool catalogDashboard: Toolsbrowses the catalog; quox tool install brings one into your organisation.

$ quox tool catalog
 Tool ID                                      Category   Risk
 powers.mcp.9f18…crystaldba_postgres-mcp      mcp        low
   crystaldba/postgres-mcp (hosted MCP)
$ quox tool install powers.mcp.9f18…crystaldba_postgres-mcp

Real output · dev catalog excerpt · captured 2026-09-09

api

Fails closed, by default.

The REST surface sits behind the same gate as every other door: no token, no answer, on every route. The exchange below is a real request against our own development collector, refused exactly as it should be.

How do I use itcurl -H 'Authorization: Bearer …'Docs: API referenceAPI keys are issued per identity and scoped like every other credential.

$ curl -s -o /dev/null -w "%{http_code}\n" \
    http://<your-instance>/api/agents
401
$ curl -s http://<your-instance>/api/agents
{"error":"authentication_required",
 "message":"Valid JWT or service key required"}

Real request · our own dev collector · captured 2026-09-09

Where it sits

Five doors, one house.

Bundled with QuoxCORE; the doors are not add-ons. Chat, the CLI and the MCP server carry their own pages, and all five answer to the same identity, permissions and evidence underneath.

if that’s not enough ...your code goes hereyour plugin can use everything underneath

you build this

QuoxChat/QuoxCLI/QuoxMCP/API docs/QuoxCORE

Ready when you are

Walk in through any door.

The dashboard, CLI, MCP server and API ship in the box with QuoxCORE: no extra licence, no extra install.

See the platform Try the live demo