Skip to main content
Use this page to get one tool invocation or AI interaction visible in the Agnost dashboard. The Agnost AI skill detects the right integration route and applies the smallest matching change.

1. Get your organization ID

  1. Sign in at app.agnost.ai.
  2. Open Settings > Organization. Copy your organization ID: it’s a UUID.
This ID is what we’ll refer to as your org_id or AGNOST_ORG_ID (also called write_key in some SDKs). Treat it as a public identifier: it routes telemetry to your workspace, but it does not grant dashboard read access on its own.
If your conversations can contain personal or sensitive data, read Data Governance before sending production traffic. Agnost does not currently provide automatic PII redaction before ingestion, so redact or pseudonymize sensitive fields in your application first.

2. Proceed with skill-based onboarding

Install the skill in your agent environment:
Then ask your coding agent to use it from your app root:
The skill asks for missing facts, detects whether your app needs SDK, MCP, or OpenTelemetry instrumentation, and keeps input/output capture enabled unless you ask to redact it. After the edit, restart or deploy your app, trigger one real chat, agent action, or MCP tool call, then confirm the event in the dashboard.

Integration guides

Use these guides if you want to wire Agnost yourself or review what the skill will detect.

AI conversations

Track LLM calls and agent turns directly from Python or TypeScript application code.

OpenTelemetry

Forward traces from OTel-enabled frameworks such as Vercel AI SDK, Mastra, LangChain, OpenAI, etc.

MCP servers

Track tool, resource, and prompt calls from a dedicated MCP server.

MCP Toolbox

Send telemetry from Google’s MCP Toolbox for Databases.

Verify

Open app.agnost.ai and check:
  • Conversations for SDK-tracked interactions
  • Tools for MCP tool invocations
  • Raw logs for the unfiltered event stream
Events usually appear within a few seconds. Nothing showing up? Check the org ID, restart/deploy state, and whether the real app path was exercised.

Next steps