vercel package adds a span processor that maps those spans onto the OpenInference conventions before they’re exported, so AgentMark reads model calls, tool calls, and token usage as normalized traces. This works with AI SDK v6.
Setup
Register OpenTelemetry and point the exporter at AgentMark
Register the span processor with
@vercel/otel. In a Next.js app this goes in instrumentation.ts at the project root. Use your AgentMark API key and app id from project settings.Run your app
Run your app as usual. Each model call and tool call arrives in AgentMark as a span, grouped into a trace. See Traces and logs.
What AgentMark captures
After the span processor maps them, Vercel AI SDK spans use the OpenInference attribute conventions — model, token usage, input and output messages, tool calls, settings, and span kind are all mapped onto AgentMark’s normalized trace fields, and token counts feed cost tracking. See OpenInference for the full attribute mapping.Next steps
OpenInference
How AgentMark reads OpenInference attributes
Traces and logs
Explore traces once they arrive
Have questions?
Reach out any time:
- Email us at hello@agentmark.co for support
- Schedule an Enterprise Demo to learn about our business solutions