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

llm-strings

v1.1.1

Published

Parse and build LLM connection strings — like database URLs, but for LLM APIs

Readme

🔗 llm-strings

Connection strings for LLMs. Like database URLs, but for AI.

npm version License TypeScript Zero Dependencies


the parts of a LLM connection string

llm://api.openai.com/gpt-5.2?temp=0.7&max=2000
llm://my-app:[email protected]/claude-sonnet-4-5?cache=5m
llm://bedrock-runtime.us-east-1.amazonaws.com/anthropic.claude-sonnet-4-5-20250929-v1:0?temp=0.5

Every LLM provider invented their own parameter names. max_tokens vs maxOutputTokens vs maxTokens. top_p vs topP vs p. stop vs stop_sequences vs stopSequences. You write the config once, then rewrite it for every provider.

llm-strings gives you a single, portable format. Parse it, normalize it to any provider's API, and validate it — all in one library with zero dependencies.

Based on the LLM Connection Strings article by Dan Levy. See draft IETF RFC for llm://.

Install

npm install llm-strings

Quick Start

import { parse, normalize, validate, build } from "llm-strings";

// Parse a connection string into structured config
const config = parse("llm://api.openai.com/gpt-5.2?temp=0.7&max=2000");
// → { host: "api.openai.com", model: "gpt-5.2", params: { temp: "0.7", max: "2000" } }

// Normalize aliases and map to the provider's actual API param names
const { config: normalized, provider } = normalize(config);
// → params: { temperature: "0.7", max_tokens: "2000" }, provider: "openai"

// Validate against provider specs (returns [] if valid)
const issues = validate("llm://api.openai.com/gpt-5.2?temp=3.0");
// → [{ param: "temperature", message: '"temperature" must be <= 2, got 3', severity: "error" }]

// Build a connection string from a config object
const str = build({ host: "api.openai.com", model: "gpt-5.2", params: { temperature: "0.7" } });
// → "llm://api.openai.com/gpt-5.2?temperature=0.7"

Why Connection Strings?

You already use them for databases: postgres://user:pass@host/db. They're compact, portable, and easy to pass through environment variables. LLM configs deserve the same treatment.

Store your entire model config in one env var:

LLM_URL="llm://my-app:[email protected]/gpt-5.2?temp=0.7&max=2000"

Switch providers by changing a string, not refactoring code:

# Monday: OpenAI
LLM_URL="llm://api.openai.com/gpt-5.2?temp=0.7&max=2000"

# Tuesday: Anthropic
LLM_URL="llm://api.anthropic.com/claude-sonnet-4-5?temp=0.7&max=2000"

# Wednesday: Bedrock in production
LLM_URL="llm://bedrock-runtime.us-east-1.amazonaws.com/anthropic.claude-sonnet-4-5-20250929-v1:0?temp=0.7&max=2000"

Your code stays the same. normalize() handles the parameter translation.

Benefits

  • One format, every provider — Write temp=0.7&max=2000 once. Normalization maps it to temperature, max_tokens, maxOutputTokens, maxTokens, or whatever your provider calls it.
  • Catch mistakes earlyvalidate() checks types, ranges, and provider-specific rules before you burn tokens on a bad request.
  • Zero dependencies — Pure TypeScript. No runtime baggage.
  • Portable config — Fits in an env var, a CLI flag, a config file, or a database column.
  • Shorthand aliases — Use temp, max, topp, freq, pres — they all expand to the right thing.

Format

llm://[label[:apiKey]@]host/model[?params]

| Part | Required | Description | Example | | ---------- | -------- | ----------------------------------------- | ------------------------------ | | label | No | App name or identifier | my-app | | apiKey | No | API key (in the password position) | sk-proj-abc123 | | host | Yes | Provider's API hostname | api.openai.com | | model | Yes | Model name or ID | gpt-5.2 | | params | No | Key-value config (query string) | temp=0.7&max=2000 |

Examples

Switching between providers

Write portable params, let normalize() translate them:

import { parse, normalize } from "llm-strings";

// Same logical config, different providers
const strings = [
  "llm://api.openai.com/gpt-5.2?temp=0.7&max=2000&top_p=0.9",
  "llm://api.anthropic.com/claude-sonnet-4-5?temp=0.7&max=2000&top_p=0.9",
  "llm://generativelanguage.googleapis.com/gemini-3-flash-preview?temp=0.7&max=2000&top_p=0.9",
];

for (const str of strings) {
  const { config, provider } = normalize(parse(str));
  console.log(`${provider}:`, config.params);
}
// openai:    { temperature: "0.7", max_tokens: "2000", top_p: "0.9" }
// anthropic: { temperature: "0.7", max_tokens: "2000", top_p: "0.9" }
// google:    { temperature: "0.7", maxOutputTokens: "2000", topP: "0.9" }

Validating before calling the API

Catch bad config before it hits the network:

import { validate } from "llm-strings";

// Anthropic doesn't allow temperature + top_p together
const issues = validate(
  "llm://api.anthropic.com/claude-sonnet-4-5?temp=0.7&top_p=0.9"
);

for (const issue of issues) {
  console.error(`[${issue.severity}] ${issue.param}: ${issue.message}`);
}
// [error] temperature: Cannot specify both "temperature" and "top_p" for Anthropic models.
// OpenAI reasoning models have different rules
const issues = validate("llm://api.openai.com/o3?temp=0.7&max=2000");
// [error] temperature: "temperature" is not supported by OpenAI reasoning model "o3".
//         Use "reasoning_effort" instead of temperature for controlling output.

Environment-driven config

import { parse, normalize } from "llm-strings";

// One env var holds the entire config
const { config, provider } = normalize(parse(process.env.LLM_URL!));

// Use the normalized params directly in your API call
const response = await fetch(`https://${config.host}/v1/chat/completions`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${config.apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    model: config.model,
    messages: [{ role: "user", content: "Hello!" }],
    ...Object.fromEntries(
      Object.entries(config.params).map(([k, v]) => [k, isNaN(+v) ? v : +v])
    ),
  }),
});

Prompt caching (Anthropic & Bedrock)

import { parse, normalize } from "llm-strings";

// cache=true → cache_control=ephemeral
const { config } = normalize(
  parse("llm://api.anthropic.com/claude-sonnet-4-5?max=4096&cache=true")
);
// → params: { max_tokens: "4096", cache_control: "ephemeral" }

// cache=5m → cache_control=ephemeral + cache_ttl=5m
const { config: withTtl } = normalize(
  parse("llm://api.anthropic.com/claude-sonnet-4-5?max=4096&cache=5m")
);
// → params: { max_tokens: "4096", cache_control: "ephemeral", cache_ttl: "5m" }

// Works on Bedrock too (Claude and Nova models)
const { config: bedrock } = normalize(
  parse(
    "llm://bedrock-runtime.us-east-1.amazonaws.com/anthropic.claude-sonnet-4-5-20250929-v1:0?cache=1h"
  )
);
// → params: { cache_control: "ephemeral", cache_ttl: "1h" }

Debugging normalization

Use verbose mode to see exactly what was transformed:

import { parse, normalize } from "llm-strings";

const { changes } = normalize(
  parse(
    "llm://generativelanguage.googleapis.com/gemini-3-flash-preview?temp=0.7&max=2000&topp=0.9"
  ),
  { verbose: true }
);

for (const c of changes) {
  console.log(`${c.from} → ${c.to} (${c.reason})`);
}
// temp → temperature            (alias: "temp" → "temperature")
// max → max_tokens              (alias: "max" → "max_tokens")
// max_tokens → maxOutputTokens  (google uses "maxOutputTokens" instead of "max_tokens")
// topp → top_p                  (alias: "topp" → "top_p")
// top_p → topP                  (google uses "topP" instead of "top_p")

Building connection strings programmatically

import { build } from "llm-strings";

const url = build({
  host: "api.openai.com",
  model: "gpt-5.2",
  label: "my-app",
  apiKey: "sk-proj-abc123",
  params: { temperature: "0.7", max_tokens: "2000", stream: "true" },
});
// → "llm://my-app:[email protected]/gpt-5.2?temperature=0.7&max_tokens=2000&stream=true"

AWS Bedrock with cross-region inference

import { parse, normalize } from "llm-strings";
import { detectBedrockModelFamily } from "llm-strings/providers";

const config = parse(
  "llm://bedrock-runtime.us-east-1.amazonaws.com/us.anthropic.claude-sonnet-4-5-20250929-v1:0?temp=0.5&max=4096"
);

detectBedrockModelFamily(config.model);
// → "anthropic"

const { config: normalized } = normalize(config);
// → params: { temperature: "0.5", maxTokens: "4096" }
//   (Bedrock Converse API uses camelCase)

Gateway providers (OpenRouter, Vercel)

import { parse, normalize, validate } from "llm-strings";

// OpenRouter proxies to any provider
const { config } = normalize(
  parse("llm://openrouter.ai/anthropic/claude-sonnet-4-5?temp=0.7&max=2000")
);
// → params: { temperature: "0.7", max_tokens: "2000" }

// Reasoning model restrictions apply even through gateways
const issues = validate("llm://openrouter.ai/openai/o3?temp=0.7");
// → [{ param: "temperature", severity: "error",
//      message: "...not supported by OpenAI reasoning model..." }]

Supported Providers

| Provider | Host Pattern | Param Style | | ----------- | ---------------------------------------- | ----------- | | OpenAI | api.openai.com | snake_case | | Anthropic | api.anthropic.com | snake_case | | Google | generativelanguage.googleapis.com | camelCase | | Mistral | api.mistral.ai | snake_case | | Cohere | api.cohere.com | snake_case | | AWS Bedrock | bedrock-runtime.{region}.amazonaws.com | camelCase | | OpenRouter | openrouter.ai | snake_case | | Vercel AI | gateway.ai.vercel.app | snake_case |

Gateways like OpenRouter and Vercel route to any upstream provider. Bedrock hosts models from multiple families (Anthropic, Meta, Amazon, Mistral, Cohere, AI21) with cross-region inference support. Each provider's parameter names differ — normalization handles the translation automatically.

Shorthand Aliases

Use these shortcuts in your connection strings — they expand automatically during normalization:

| Shorthand | Canonical | | -------------------------------------------------------------------- | -------------------- | | temp | temperature | | max, max_out, max_output, max_output_tokens, maxTokens, maxOutputTokens, max_completion_tokens | max_tokens | | topp, topP, nucleus | top_p | | topk, topK | top_k | | freq, freq_penalty, frequencyPenalty, repetition_penalty | frequency_penalty | | pres, pres_penalty, presencePenalty | presence_penalty | | stop_sequences, stopSequences, stop_sequence | stop | | random_seed, randomSeed | seed | | candidateCount, candidate_count, num_completions | n | | reasoning, reasoning_effort | effort | | cache_control, cacheControl, cachePoint, cache_point | cache |

Sub-path Imports

For smaller bundles, import only what you need:

import { parse, build } from "llm-strings/parse";
import { normalize } from "llm-strings/normalize";
import { validate } from "llm-strings/validate";
import { detectProvider, ALIASES, PROVIDER_PARAMS, PARAM_SPECS } from "llm-strings/providers";

All sub-paths ship ESM + CJS with full type declarations.

API Reference

parse(connectionString): LlmConnectionConfig

Parses an llm:// connection string into its component parts. Throws if the scheme is not llm://.

build(config): string

Reconstructs a connection string from a config object. Inverse of parse().

normalize(config, options?): NormalizeResult

Normalizes parameters for the target provider:

  1. Expands shorthand aliases (temptemperature)
  2. Maps to provider-specific param names (max_tokensmaxOutputTokens for Google)
  3. Normalizes cache values (cache=truecache_control=ephemeral)
  4. Adjusts for reasoning models (max_tokensmax_completion_tokens for o1/o3/o4)

Pass { verbose: true } to get a detailed changes array documenting each transformation.

validate(connectionString, options?): ValidationIssue[]

Parses, normalizes, and validates a connection string against provider-specific rules. Returns [] if everything is valid. Checks:

  • Type correctness (number, boolean, string enums)
  • Value ranges (e.g., temperature 0–2 for OpenAI, 0–1 for Anthropic)
  • Mutual exclusions (temperature + top_p on Anthropic)
  • Reasoning model restrictions (no temperature on o1/o3/o4)
  • Bedrock model family constraints (topK only for Claude/Cohere/Mistral)

Pass { strict: true } to promote warnings (unknown provider, unknown params) to errors:

validate("llm://custom-api.com/my-model?temp=0.5", { strict: true });
// → [{ severity: "error", message: "Unknown provider …" }]

detectProvider(host): Provider | undefined

Identifies the provider from a hostname string.

detectBedrockModelFamily(model): BedrockModelFamily | undefined

Identifies the model family (anthropic, meta, amazon, mistral, cohere, ai21) from a Bedrock model ID. Handles cross-region (us., eu., apac.) and global inference profiles.

detectGatewaySubProvider(model): Provider | undefined

Extracts the underlying provider from a gateway model string (e.g. "anthropic/claude-sonnet-4-5""anthropic"). Returns undefined for unknown prefixes or models without a /.

isReasoningModel(model): boolean

Returns true for OpenAI reasoning models (o1, o3, o4 families). Handles gateway prefixes like "openai/o3".

isGatewayProvider(provider): boolean

Returns true for gateway providers (openrouter, vercel) that proxy to other providers.

canHostOpenAIModels(provider): boolean

Returns true for providers that can route to OpenAI models and need reasoning-model checks (openai, openrouter, vercel).

bedrockSupportsCaching(model): boolean

Returns true if the Bedrock model supports prompt caching (Claude and Nova models only).

Constants

| Export | Description | | --- | --- | | ALIASES | Shorthand → canonical param name mapping | | PROVIDER_PARAMS | Canonical → provider-specific param names, per provider | | PARAM_SPECS | Validation rules (type, min/max, enum) per provider, keyed by provider-specific param name | | REASONING_MODEL_UNSUPPORTED | Set of canonical params unsupported by reasoning models | | PROVIDER_META | Array of provider metadata (id, name, host, brand color) for UI integrations | | MODELS | Suggested model IDs per provider | | CANONICAL_PARAM_SPECS | Canonical param specs per provider with descriptions — useful for building UIs |

TypeScript

Full type definitions ship with the package:

// Core types from the main entry
import type {
  LlmConnectionConfig,
  NormalizeResult,
  NormalizeChange,
  NormalizeOptions,
  ValidateOptions,
  ValidationIssue,
} from "llm-strings";

// Provider types from the providers sub-path
import type {
  Provider,
  BedrockModelFamily,
  ParamSpec,
  ProviderMeta,
  CanonicalParamSpec,
} from "llm-strings/providers";

Provider Metadata (for UI integrations)

The library exports metadata useful for building UIs — provider names, brand colors, suggested models, and canonical parameter specs:

import { PROVIDER_META, MODELS, CANONICAL_PARAM_SPECS } from "llm-strings/providers";

// Provider display info
PROVIDER_META.forEach((p) => console.log(`${p.name}: ${p.host} (${p.color})`));
// OpenAI: api.openai.com (#10a37f)
// Anthropic: api.anthropic.com (#e8956a)
// ...

// Suggested models per provider
MODELS.openai;    // → ["gpt-5.2", "gpt-5.2-pro", "gpt-4.1", "gpt-4.1-mini", ...]
MODELS.anthropic; // → ["claude-opus-4-6", "claude-sonnet-4-6", "claude-sonnet-4-5", ...]

// Canonical param specs — useful for building config forms
CANONICAL_PARAM_SPECS.openai.temperature;
// → { type: "number", min: 0, max: 2, default: 0.7, description: "Controls randomness" }

CANONICAL_PARAM_SPECS.anthropic.effort;
// → { type: "enum", values: ["low", "medium", "high", "max"], default: "medium", description: "Thinking effort" }

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT


📖 Read the spec · 🐛 Report a bug · 💡 Request a feature