Skip to Content
DocsConfigurationPublic APIs, Agents & MCPOverview

Public APIs, Agents & MCP

Workbench2 is the operator control plane. It exposes two HTTP APIs, two kinds of credentials, an in-app Ecosystem Agent, and a Workbench MCP server. Those surfaces are not the Java Runtime scoring APIs (POST /invocations then POST /response).

Administration → API Keys — Public API Access vs Private Ecosystem Keys

Open Administration → API Keys (admin role). Switch Public API Access and Private Ecosystem Keys. Agents is the neighbouring tab.

Surfaces at a glance

SurfaceDefault local URLWho uses itAuth
Private Workbench APIhttp://localhost:8001/api/v1Workbench SPA, Campaign Management, internal servicesWorkbench session JWT (Authorization: Bearer)
Public API gatewayhttp://localhost:8004/public/v1Notebooks, partners, MCP harness, external appsOne credential: public key or Workbench JWT
Workbench MCPPOST http://localhost:8001/mcpEcosystem Agent, Cursor, Claude CodeIn-process for /assistant; public key or JWT for HTTP MCP
LLM proxyPOST http://localhost:8001/v1/messagesAgent SDK / Claude CodeWorkbench JWT; no Anthropic key in the image
Runtime scoringhttp://localhost:8091/invocationsProduction apps, Runtime DashboardRuntime config; closed loop uses /response (singular)
Runtime MCPPOST http://localhost:8091/mcpAgents that score campaignsSeparate from Workbench MCP

./backend/run.sh starts the private API on 8001 and the public gateway on 8004. The Vite UI on 5270 talks to :8001 and does not proxy /mcp.

Which credential?

Public credentials (ewb_public_…) never replace private ecosystem JWTs. Issue scoped public keys for integrations. Keep private keys for Grafana, ecosystem-server, and other platform services that expect a generated ecosystem JWT.

CredentialTabPrefix / shapePurpose
Public API AccessPublic API Accessewb_public_…Scoped gateway + HTTP MCP. Shown once on create/rotate.
Private Ecosystem KeysPrivate Ecosystem KeysServer-generated JWTGrafana, ecosystem-server, platform services. Stored in ecosystem_meta.api_keys.

Create public credentials with an owner (user, service account, organization, or partner), optional expiry, and scopes. The Public APIs sub-tab shows which routes the selected scopes unlock.

Typical access paths

  1. Browser operator — sign in to Workbench. The SPA uses the private API with your session JWT. No public key.
  2. External integration — mint a public credential, link an internal API key on that credential, call :8004/public/v1/… with X-API-Key (or Bearer public key). JWT login is optional when you use a public key alone.
  3. Ecosystem Agent — Administration → Agents or /assistant. In-process MCP; no public key.
  4. Cursor / Claude Code — POST /mcp with a public key or JWT, plus ANTHROPIC_BASE_URL pointing at Workbench :8001 for POST /v1/messages.
  5. Campaign scoring — Runtime POST /invocations then POST /response. Workbench MCP score_customer / send_feedback wrap a deployment; they are not Runtime POST /mcp.

Pages in this section

  • Active Directory & SSO — Microsoft Entra ID (Azure AD) OIDC, On-Premises AD (LDAP/LDAPS), corporate Auto-SSO, and group-to-role mapping
  • API Keys — issue, rotate, revoke
  • Public APIs — gateway routes and scopes
  • Private APIs — :8001/api/v1 routers
  • Agents — product catalog and Ecosystem Agent
  • MCP — Workbench vs Runtime vs sidecar

Related: API Management (test Runtime scoring from Workbench), Runtime API Access, Runtime MCP.

Last updated on