<!-- Full-page Markdown export (rendered HTML → GFM). Source: https://neotoma.io/ur/inspector Generated: 2026-04-27T12:48:26.767Z --> # Inspector The Inspector is the visual operator console for any Neotoma instance. It runs alongside the Neotoma server (locally at `http://localhost:3080/inspector`, or on a hosted Neotoma deployment) and is the fastest way to see exactly what your agents have written, why, and on whose authority. Where the CLI and MCP surface let agents *write* to Neotoma, the Inspector lets *you* read, audit, and correct that state, every entity, every observation, every relationship, every source artifact, every signed agent, every conversation turn, without writing SQL. inspector.neotoma.io/ Inspector Neotoma Dashboard Conversations Turns Compliance Activity Feedback Entities Observations Sources Relationships Graph Explorer Schemas Timeline Interpretations Agents Agent grants Settings Dashboard Live state of this Neotoma instance Healthyv0.12.0 Entities 12,481 +128 today Observations 84,302 +1,021 today Relationships 6,907 Agents 14 3 hardware Entities by type - agent\_message4,910 - transaction3,104 - contact2,231 - task1,556 - event902 Recent timeline events - 12:41storetransaction · "Subscription · Vercel" - 12:38correctcontact · canonical\_name updated - 12:30storeconversation\_message · turn 4 - 12:21linkPART\_OF created Inspector dashboard with system stats, entity-type histogram, recent timeline events, and agent attribution coverage. ## What the Inspector is for Neotoma's value comes from a single shared, versioned graph of state. Once agents start writing, three questions immediately matter: - **What did they write?** Browse entities, observations, sources, relationships, and timeline events with full filters and pagination. - **Why is the snapshot what it is?** Drill into per-field provenance, which observation won, when, from which agent, citing which source row. - **Was it written on real authority?** Inspect AAuth trust tiers, JWT subjects, hardware attestation envelopes, and operator allowlists per row. Because Neotoma never overwrites observations, the Inspector also acts as a forensic tool: every value you see can be traced back to the observation, source, and agent that produced it, and corrections layer on top without erasing history. ◆ ## How to open it The Inspector is bundled with the Neotoma server and served by the same process as the API: \# Start (or confirm) the local API neotoma api start --env dev # Open the Inspector open http://localhost:3080/inspector For hosted Neotoma deployments, the Inspector is reachable at `https://<your-neotoma-host>/inspector`. The Inspector respects the same authentication contract as the API: bearer tokens, `user_id` scope, and AAuth-attributed writes flow through unchanged. See [AAuth](/aauth) for the attribution contract surfaced in every Inspector list. ◆ ## Sections Each subpage below maps directly to a section of the Inspector application and shows representative UI: - [Dashboard & health](/inspector/dashboard) , top-level stats, type breakdown, system health, attribution coverage. - [Entities](/inspector/entities) , filter, search, and inspect entity snapshots; per-field provenance and multi-field corrections. - [Observations & sources](/inspector/observations-and-sources) , the immutable write log and the raw artifacts behind it. - [Relationships & graph](/inspector/relationships-and-graph) , typed edges, neighborhood graph explorer, traversal. - [Schemas](/inspector/schemas) , registered entity types, fields, identity rules, schema evolution. - [Timeline & interpretations](/inspector/timeline) , event stream, replays, derived interpretation entities. - [Conversations & turns](/inspector/conversations) , agent\_message rows reconstructed into per-conversation transcripts. - [Agents, AAuth & grants](/inspector/agents) , per-agent rosters, trust tier, attestation envelopes, grant policies. - [Search](/inspector/search) , ⌘K global identifier and full-text search across every record type, with ranking and result-kind details. - [Feedback](/inspector/feedback) , in-app route `/feedback` (top-level sidebar, not under Settings): submissions, PII redaction preview, and status feed. - [Settings](/inspector/settings) , `/settings` instance configuration. Drill in for [Connection](/inspector/settings/connection), [Attribution policy](/inspector/settings/attribution-policy), [Retention](/inspector/settings/retention), and [Theme & accessibility](/inspector/settings/theme). ◆ ## Tech stack Inspector is a standalone React 19 + Vite 6 single-page application served from the Neotoma server. It uses Tailwind CSS for styling, TanStack Query for data fetching, TanStack Table for list views, Recharts for charts, and `@xyflow/react` for the graph explorer. Every panel reads from the same REST endpoints documented under [REST API](/api) , there is no Inspector-specific backend. ◆ ## Read-mostly, with safe corrections The Inspector is read-mostly by design. Where it does write, it follows the same rules as any other client: - Field-level corrections add a new observation; they never mutate or delete the prior one. - Relationship creates and merges go through the same `/create_relationship` and `/merge_entities` endpoints used by the MCP and CLI. - Inspector-originated writes are themselves attributed, `clientInfo.name` is set to `inspector-ui` and (when configured) signed via AAuth, so you can audit operator actions in the same surfaces as agent actions.