From 34851e9cae44d31e37deaa51ebf34548ee9d664f Mon Sep 17 00:00:00 2001 From: Nivedit Jain Date: Fri, 24 Jul 2026 14:08:11 +0000 Subject: [PATCH 1/2] docs(agenteye): note the REST API in the overview MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a value-level mention that the dashboard and CLI are backed by a REST API you can call with a scoped key — in the overview's Interfaces list and the component summary. No endpoint signatures; the exhaustive reference stays in the enterprise docs. Co-Authored-By: Claude Opus 4.8 --- docs/agenteye/overview.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/agenteye/overview.mdx b/docs/agenteye/overview.mdx index f3271261..c979f1d9 100644 --- a/docs/agenteye/overview.mdx +++ b/docs/agenteye/overview.mdx @@ -71,6 +71,7 @@ Failproof AI Observability is organized around three ideas (**observe**, **analy - **[CLI](/agenteye/cli-and-agents)**: drive your whole deployment from the terminal or a script, and let a coding agent do it for you in plain English. - **[AI assistant](/agenteye/assistant)**: ask questions about your agents in plain English, right inside the dashboard. +- **REST API**: everything the dashboard and CLI do is backed by a REST API you can call directly with a scoped [API key](/agenteye/api-keys) — ingest events, query sessions and evaluations, and manage dashboards, alerts, audits, users, and keys, so you can wire Failproof AI Observability into your own tooling. **Admin** (run it for your team): @@ -86,7 +87,7 @@ Data flows in one direction, from your agent code to the dashboard: your agent ( - **Python SDK**: you add a few `agenteye.event.*` calls to your agent; events are buffered locally. - **agenteye-collector**: a lightweight daemon on each agent machine that batches events and ships them to the server. -- **Server**: ingests your events and keeps operational state in your own databases. +- **Server**: ingests your events, keeps operational state in your own databases, and serves the REST API that the dashboard, CLI, and your own integrations all use. - **Dashboard**: where you explore everything. - **Optional services**: a scoring service (evaluations), and an AI assistant service (the in-dashboard chat). From 826c821225afad0000e90730223426f0a97a2bdf Mon Sep 17 00:00:00 2001 From: Nivedit Jain Date: Fri, 24 Jul 2026 14:09:14 +0000 Subject: [PATCH 2/2] docs(changelog): add entry for #593 Co-Authored-By: Claude Opus 4.8 --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 88b10a4a..aa68350d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -21,6 +21,7 @@ ### Docs - Add a Codex session capture page for AgentEye: what the collector picks up from local OpenAI Codex sessions (CLI, IDE, desktop app), how to turn it on with an `events:add` key, and where captured sessions show up. Value/contract level only, no implementation detail. (#592) +- Note in the AgentEye overview that the dashboard and CLI are backed by a REST API callable with a scoped key, so prospects can see a programmatic API exists. Gist/contract level only — no endpoint signatures; the exhaustive HTTP API reference stays in the enterprise docs. (#593) ## 0.0.14-beta.3 — 2026-07-20