Getting started

Quickstart

Send your first AI interaction to Voxmith

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

1. Get your organization ID

  1. Sign in at app.voxmith.com.
  2. Open Settings > Organization. Copy your organization ID: it's a UUID.

In these docs, org_id and VOXMITH_ORG_ID both mean your organization ID. It routes telemetry to your workspace but does not grant dashboard read access.

2. Set up your application

Install the skill in your agent environment:

npx skills add Voxmith/skills --skill voxmith

Then ask your coding agent to use it from your app root:

Use the voxmith skill to add Voxmith analytics.
Org ID: your-org-id
Target app: .
Verification: local app
Entrypoint: the real chat route, agent call, MCP server startup, or tool call

The skill asks for missing facts, detects whether your app needs SDK, MCP, or OpenTelemetry instrumentation, and verifies the resulting setup.

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.


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:

  • Voxmith skill — recommended; it inspects, instruments, and verifies your app.
  • Voxmith SDK — manually wrap the framework call you want to analyze.
  • OpenTelemetry — connect existing framework telemetry to Voxmith.

Use one approach for a given call path at first. Enabling the SDK and OpenTelemetry around the same call can create duplicate interactions.


Verify

Open app.voxmith.com and check:

  • Conversations for SDK-tracked interactions
  • Tool calls for MCP tool invocations
  • Events 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

  • Conversations: review the complete interaction you sent.
  • Events: inspect the underlying telemetry and verify its fields.
  • Intents: organize production conversations by what users wanted.