1. Get your organization ID
- Sign in at app.agnost.ai.
- Open Settings > Organization. Copy your organization ID: it’s a UUID.
org_id and AGNOST_ORG_ID both mean your organization ID. It
routes telemetry to your workspace but does not grant dashboard read access.
2. Give this prompt to your coding agent
From the root of the application you want to monitor, give your coding agent this single prompt. Replaceyour-org-id with the value from step 1.
Setup prompt
The
npx command requires Node.js 18 or later. If your application does not use
Node.js, the command still installs the agent skill; it does not add Node.js to
your application runtime.3. Run one real interaction
After the agent finishes its edits:- Restart the application with its normal development command.
- Trigger one real chat, agent action, or MCP tool call through the application.
- Keep the Agnost onboarding screen open. It checks for incoming data automatically.
Setup guides
Continue in the Get started sidebar and select the framework or application type you already use. Each AI framework guide keeps all three approaches together:- Agnost AI skill — recommended; it inspects, instruments, and verifies your app.
- Agnost AI SDK — manually wrap the framework call you want to analyze.
- OpenTelemetry — connect existing framework telemetry to Agnost AI.
Agent frameworks
Set up Agnost AI for Agno, Anthropic, CrewAI, DSPy, LangChain, Mastra, OpenAI, and more.
Custom applications
Track custom Python or TypeScript AI interactions, or connect an existing OTel pipeline.
MCP servers
Track tool, resource, and prompt calls from a dedicated MCP server.
Platforms
Set up MCP Toolbox or Apify telemetry.
Verify your first useful trace
When the onboarding screen confirms the first event, choose Inspect first event. Verify these fields before sending more traffic:- The input and output match the interaction you just ran.
- The user ID remains stable for the same user.
- The conversation or session ID groups related turns together.
- The success or error state is accurate.
- The agent, model, and tool names identify the real execution path.
- Tool spans appear under the turn that invoked them when your framework emits hierarchy.
Nothing appeared
Check these in order:- The application was restarted after environment or startup changes.
- The configured organization ID matches the current Agnost workspace.
- The interaction exercised the instrumented entrypoint rather than a test or fallback path.
- Application logs do not show exporter, network, or package errors.
- Only one integration wraps the call path; duplicate SDK and OpenTelemetry setup can create confusing results.
Turn the first trace into a failure detector
One event proves transport, not monitoring value. Complete the activation loop:- Open Violations and define one expected behavior that can be judged from a conversation.
- Run a representative interaction that should pass or fail that rule.
- Open the supporting conversation before accepting the finding.
- When the same issue recurs, review its recommendation in Auto-improve and inspect any proposed code change before shipping it.
Next steps
- Conversations: review the complete interaction you sent under Users.
- Events: inspect the underlying telemetry and verify its fields.
- Violations: define expected behavior and review failures.
- Improvements: understand how evidence becomes a proposed fix.