Reference

Every page here is a contract you integrate against. No page describes internal processing.

Assistant Kit (host-facing)

How your frontend drives the widget.

Client command API Every diosc() command, with signatures.

Web component API The attributes and the events you can subscribe to.

Server API (backend-to-backend)

The HTTP endpoints your own services call.

Server API Auth binding, MCP file access, and knowledge-base sync.

Coming next

These contracts land per the documentation structure spec:

• MCP contract specification: what an MCP server must implement (tool fields, auth forwarding, response shapes).
• Configuration schema: the admin-portal-visible knobs.
• Audit log schema: event taxonomy and field semantics.