8eight.
BUILD · TEST · PUBLISH

Agents that work.
Boundaries that hold.

Create an agent, route model calls through the server, and publish a website widget. No invented analytics. No provider keys in browser code.

AceID workspace gate Server-side secrets Self-hosted widget
eight / workspace Workspace preview
WORKSPACE

Agent setup

Draft
Agent instructionsRole · constraints · success criteria01
Server-side model routeGroq or OpenAI provider Ready
Embed after publishingSDK
<script src="/widget.js" defer></script>
Explicit boundariesValidation on the server
Ready to embedOne script tag
ONE WORKSPACEREAL INFERENCEEMBED-READY UI
01 / PLATFORM

Small surface area.
Clear control.

Eight focuses on the path from agent configuration to a working interface, without pretending sample counters are production telemetry.

01AGENT BUILDER

Configure the agent

Set instructions, choose a supported model, and manage draft or published state.

02MODEL ROUTE

Run real inference

Use the validated server endpoint with Groq or OpenAI. Keys are never shipped to the browser.

03WIDGET SDK

Embed the interface

Use the self-hosted widget script or mount the JavaScript SDK to control the chat panel.

04RUNTIME SAFETY

Keep access scoped

OIDC session validation protects the workspace, and tool execution stays allowlisted.

05IDENTITY

Workspace sign-in

AceID gates the builder. Local drafts are namespaced to the signed-in account in this browser.

06DEVELOPER SURFACE

One script to embed

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>
02 / WORKFLOW

From draft to
useful output.

Four practical steps, with errors visible when setup is incomplete.

01Describe the job

Set instructions and a supported model.

02Test the route

Send prompts through the real server endpoint.

03Publish the widget

Copy the script and mount the chat panel.

04Verify deployment

Keep provider and identity configuration on the server.

03 / RUNTIME

No secret belongs
in the page source.

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.

Sign in with AceID