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

@axrail/model-ai-sdk

v0.2.0-alpha.1

Published

Vercel AI SDK model bridge for Axrail AgentModelProvider.

Readme

@axrail/model-ai-sdk

Vercel AI SDK bridge for Axrail's stable AgentModelProvider contract.

Status: post-RC / v0.2 development. Requires Node.js 22.13+.

Purpose

Axrail should not maintain separate HTTP request/response protocol adapters for every model vendor.

@axrail/interaction-sdk
       ↓
AgentModelProvider
       ▲
@axrail/model-ai-sdk
       ↓
Vercel AI SDK LanguageModel
       ↓
OpenAI / Anthropic / Google / Azure / Bedrock / compatible providers

The bridge performs one model step. Axrail AgentLoop still owns tool execution and multi-step reasoning.

Example

import { anthropic } from "@ai-sdk/anthropic";
import { AiSdkModelProvider } from "@axrail/model-ai-sdk";

const provider = new AiSdkModelProvider({
  id: "claude-sonnet",
  model: anthropic("claude-sonnet-4-5"),
});

interaction.models.register({
  descriptor: {
    id: "claude-sonnet",
    providerId: "anthropic",
    capabilities: {
      toolCalling: true,
      reasoning: true,
    },
  },
  provider,
});

Provider-specific packages and credentials are owned by the embedding application.

Governance boundary

The bridge gives Vercel AI SDK tool schemas without execute handlers.

Therefore:

AI SDK produces tool call
        ↓
Axrail AgentLoop
        ↓
Axrail ToolRuntime
        ↓
Policy / Approval / Audit
        ↓
Tool execution

Vercel AI SDK does not become a second engineering Tool runtime.

Existing provider

@axrail/model-openai-compatible remains available as a lightweight/reference compatibility implementation. New vendor integrations should prefer AI SDK provider packages through this bridge.