How it works
Key concepts
| Concept | Description |
|---|---|
| Org ID | Your workspace identifier. All events are scoped to an org. Get it from app.agnost.ai. |
| Session | A single conversation or agent run. Groups related events together. |
| Event | A single tool/function call within a session. Has a name, latency, success/failure, and optional input/output. |
| Checkpoint | A named timing point inside an event — useful for profiling multi-step tools. |
| User | An optional identity attached to a session via user_id for per-user analytics. |
MCP Servers
One-line integration. Wrap your MCP server and every tool, resource, and prompt call is tracked automatically.TypeScript
MCP server in TypeScript
Python FastMCP
MCP server with FastMCP
Go
MCP server in Go
Anthropic (low-level)
Low-level Anthropic Python SDK
Conversational Agents
For non-MCP agents. Usebegin() / end() to wrap any AI interaction and track it manually.
