Citations on every turn
Agent never claims a number without naming the row + column it came from. Click the citation, jump to the row in the dataset.
Two modes from one engine. Chat — conversational access for business users, with citations on every turn. MCP server — DAVA's tools exposed over the Model Context Protocol so customer agents (Claude Desktop, custom) can call them.
Agent is how non-technical stakeholders interact with the cleaned data. Every chat turn is hash-chained: who asked what, what tools were called, what data was returned. In Decisioning mode, write tools require human approval.
Each capability runs in the shared engine — the Norm pipeline, the Trust audit chain, the Decisioning mode toggle. Same substrate as the other four products.
Agent never claims a number without naming the row + column it came from. Click the citation, jump to the row in the dataset.
Default analytical assistant or one of three specialized profiles: medical-icu (deterioration risk), finance-fund-anomaly (NAV/performance), public-sector-irregularity (tax/permit flagging). Each tunes the system prompt + tool selection.
DAVA's read tools exposed over the Model Context Protocol. Plug into Claude Desktop or a custom agent. Six tools today: trust events, lineage, policies, norm preview, connect results, agent sessions.
Assistive (default): the agent suggests, the human acts. Decisioning: write tools execute under contract amendment. Mode toggle is a per-org setting; every session inherits and audits the mode.
The Python SDK is the most mature. TypeScript follows the same shape. Both ship with strict types and async-first APIs.
Same auth as the rest of DAVA: bearer API key on Authorization: Bearer dava_live_… or session cookie + CSRF for browser flows.
We'll run your hardest dataset through DAVA Agent during a 5-day pilot. You keep the cleaned output and the evidence pack either way.