AI Database Querying

Need data? File a ticket. Bug an engineer. Wait.

Adam lets anyone ask in plain English and get real answers from real databases.

How ATI Tool Calling Works

1

User sends chat request with database endpoint references

2

Adam connects to each endpoint's ATI server and discovers tools

3

Tool definitions sent to LLM alongside the conversation

4

LLM decides whether to call tools based on context

5

Adam verifies RBAC: does this user have access?

6

Tool result fed back into conversation (max 12 iterations)

Same permissions as the user. Always.

RBAC-Scoped AI Access

The AI operates under the exact same permissions as the requesting user. No privilege escalation , because the AI is authenticated through the same identity system.

  • Read-only if user is read-only
  • Invisible endpoints stay invisible
  • Same identity system for AI and data

Natural Language Queries

Ask questions about your data in plain English. AI queries your databases directly through ATI, constrained by your RBAC permissions.

  • No SQL required
  • Context-aware responses
  • Multi-database support

ATI Tool Orchestration

Up to 12 tool passes per turn. AI discovers available tools via cursor-based pagination, calls databases mid-conversation, and feeds results back into the conversation.

  • Namespace-qualified tools , {client}__{tool} for multi-tenant isolation
  • Cursor-based tool discovery with cached snapshots
  • Two tool sources: managed Adam endpoints + user-registered ATI servers

Tool Execution Metrics

Every tool call is instrumented with OpenTelemetry. Track attempts, failures, and latency per tool and per server.

  • Attempt & failure counters
  • Latency histograms
  • Per-tool observability

Conversation Persistence

Conversations stored in Postgres with two modes: persistent for long-running analysis, ephemeral for one-off queries. Full sequence tracking across sessions.

  • Persistent and ephemeral conversation modes
  • SSE streaming with heartbeat keep-alive
  • Resume conversations across sessions

Token Accounting

Prompt and completion tokens tracked per conversation, per user, per organization. Know exactly what your AI usage costs across every provider.

  • Per-conversation token tracking
  • Prompt and completion breakdowns
  • Organization-level usage aggregation

See what your team has been missing.

Everyone who sees Adam wants it for a different reason. The common thread: they can't reach their own data.