This page gets one tool invocation or AI interaction visible in the Agnost dashboard. Pick the path that matches what you’re building.Documentation Index
Fetch the complete documentation index at: https://docs.agnost.ai/llms.txt
Use this file to discover all available pages before exploring further.
1. Get your organization ID
- Sign in at app.agnost.ai.
- Open Settings → Organization. Copy your organization ID: it’s a UUID.
org_id (also called write_key in some SDKs). Treat it as a public identifier: it does not grant write access on its own.
2. Pick a path
MCP server
Track tool invocations on a Model Context Protocol server. Python, TypeScript, or Go.
AI conversations
Track LLM calls / agent turns from any Python or Node application.
OpenTelemetry agent
You’re already running Vercel AI SDK, Mastra, OpenAI Agents, LangChain, etc. and want to forward traces.
MCP Toolbox
Google’s
genai-toolbox for databases. One-flag setup.Path A: MCP server
- Python (FastMCP)
- Python (low-level)
- TypeScript
- Go
Path B: AI conversations
For tracking LLM calls or agent turns directly from your application code (no MCP).- Python
- TypeScript
Path C: OpenTelemetry
If you’re already exporting OTel traces from a supported framework, point them at Agnost using theX-Agnost-Org-ID header:
Verify
Open app.agnost.ai and check:- Tools: for MCP tool invocations
- Conversations: for
begin/endinteractions - Raw logs: for the unfiltered event stream
Troubleshooting
- No data after 30 seconds: confirm the org ID is correct (Settings → Organization), and that
endpointdefaults tohttps://api.agnost.ai. For OTel, confirm the header name isX-Agnost-Org-ID(case-insensitive but the dash placement matters). ModuleNotFoundError: mcp: the Python MCP SDK depends on the officialmcp>=1.10package. Install it viapip install mcp(agnost-mcplists it as a dependency).- Authentication errors: org ID alone is enough for SDK ingestion. For programmatic dashboard access, see Authentication.
Next steps
- SDK index: every published package and its canonical import.
- Authentication: API keys and JWT for the REST API.
- Errors: error response schema and status codes.
- Architecture: how ingestion, processing, and the dashboard fit together.
