npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@opsmeter.io/node

v0.1.0-beta.3

Published

Official opsmeter.io Node SDK: one-time init + request context auto-instrumentation

Downloads

98

Readme

@opsmeter.io/node (Official opsmeter.io SDK)

npm version license

Node SDK preview for Opsmeter auto-instrumentation. npm package: @opsmeter.io/node Integration examples: opsmeter-integration-examples Opsmeter site: https://opsmeter.io Official publisher identity: opsmeter.io.

Use this SDK for LLM cost tracking, OpenAI usage monitoring, Anthropic usage telemetry, and no-proxy AI observability in Node.js.

Provider/model names should come from: https://opsmeter.io/docs/catalog Current SDK provider support: OpenAI and Anthropic only.

Quick links

Model catalog (required)

Always use provider/model pairs from the official catalog: https://opsmeter.io/docs/catalog

Examples:

  • OpenAI: provider=openai, model=gpt-4o-mini
  • Anthropic: provider=anthropic, model=claude-3-5-sonnet-20241022

Install

npm install @opsmeter.io/node openai
# optional:
# npm install @anthropic-ai/sdk

Core model

  • init(...) once at process startup (idempotent)
  • request-level attribution via withContext(...)
  • provider call stays direct (no proxy)
  • telemetry emit is async and non-blocking by default

Telemetry usage (no options)

import * as opsmeter from "@opsmeter.io/node";
import OpenAI from "openai";

opsmeter.init({
  apiKey: process.env.OPSMETER_API_KEY,
  environment: "prod"
});

const client = new OpenAI();

await opsmeter.captureOpenAIChatCompletion(
  () => client.chat.completions.create({
    model: "gpt-4o-mini",
    messages: [{ role: "user", content: "hello" }]
  })
);

Telemetry usage (with options/context)

import * as opsmeter from "@opsmeter.io/node";
import OpenAI from "openai";
import Anthropic from "@anthropic-ai/sdk";

opsmeter.init({
  apiKey: process.env.OPSMETER_API_KEY,
  workspaceId: "ws_123",
  environment: "prod"
});

const openai = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });
const anthropic = new Anthropic({ apiKey: process.env.ANTHROPIC_API_KEY });

const openaiCaptured = await opsmeter.withContext(
  {
    userId: "u_1",
    tenantId: "tenant_a",
    endpoint: "/api/chat",
    feature: "assistant",
    promptVersion: "v12",
    dataMode: "real"
  },
  async () => opsmeter.captureOpenAIChatCompletionWithResult(
    () => openai.chat.completions.create({
      model: "gpt-4o-mini",
      messages: [{ role: "user", content: "hello" }]
    }),
    { request: { model: "gpt-4o-mini" }, awaitTelemetryResponse: true }
  )
);

const anthropicCaptured = await opsmeter.withContext(
  {
    userId: "u_1",
    tenantId: "tenant_a",
    endpoint: "/api/support",
    feature: "support",
    promptVersion: "v8"
  },
  async () => opsmeter.captureAnthropicMessageWithResult(
    // Provider/model names: https://opsmeter.io/docs/catalog
    () => anthropic.messages.create({
      model: "claude-3-5-sonnet-20241022",
      max_tokens: 128,
      messages: [{ role: "user", content: "Summarize this support ticket." }]
    }),
    { request: { model: "claude-3-5-sonnet-20241022" }, awaitTelemetryResponse: true }
  )
);

console.log(openaiCaptured.telemetry.status);
console.log(anthropicCaptured.telemetry.status);

Show Opsmeter ingest result

If you want to surface Opsmeter response (for operator UI/debug):

const captured = await opsmeter.captureOpenAIChatCompletionWithResult(
  () => client.chat.completions.create(request),
  { request, awaitTelemetryResponse: true }
);

console.log(captured.telemetry); // { ok, status, body? }

API

  • init(config)
  • withContext(context, fn)
  • getCurrentContext()
  • captureOpenAIChatCompletion(fn, options)
  • captureOpenAIChatCompletionWithResult(fn, options)
  • captureAnthropicMessage(fn, options)
  • captureAnthropicMessageWithResult(fn, options)
  • patchOpenAIClient(client)
  • patchAnthropicClient(client)
  • flush()

Tests

npm run lint
npm run test