Configure the agent
Set instructions, choose a supported model, and manage draft or published state.
Create an agent, route model calls through the server, and publish a website widget. No invented analytics. No provider keys in browser code.
<script src="/widget.js" defer></script>Eight focuses on the path from agent configuration to a working interface, without pretending sample counters are production telemetry.
Set instructions, choose a supported model, and manage draft or published state.
Use the validated server endpoint with Groq or OpenAI. Keys are never shipped to the browser.
Use the self-hosted widget script or mount the JavaScript SDK to control the chat panel.
OIDC session validation protects the workspace, and tool execution stays allowlisted.
AceID gates the builder. Local drafts are namespaced to the signed-in account in this browser.
Publish an agent and copy the generated widget snippet, or control the panel through the JavaScript SDK.
<script src="https://eight.ace-base.cc/widget.js" defer></script>Four practical steps, with errors visible when setup is incomplete.
Set instructions and a supported model.
Send prompts through the real server endpoint.
Copy the script and mount the chat panel.
Keep provider and identity configuration on the server.
Inference credentials are read by the API route. The widget receives public agent configuration, not provider credentials. Authentication is checked before private workspace routes render.