From pricing
Start Here. Use when the user asks about Narev Cloud, the Pricing API, model pricing (API reference skill vs applied workflows on top of that API), live LLM pricing, token costs, cost calculation, pinning or snapshotting model rates, Narev SDK, @ai-billing/core, provider middleware packages, Vercel AI SDK billing, Next.js App Router route handlers, @ai-billing/nextjs billing UI, narev-nextjs (greenfield and brownfield), framework-specific billing patterns, usage-based billing, billing integrations (Polar preferred; Stripe, OpenMeter/Kong, Lago also supported), benchmarks, routers, routing API, FOCUS format, Narev Self-Hosted, deployment, COGS, customer tagging, FinOps for AI, or this documentation site. Automatically routes to the specific skill or documentation path based on their task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pricing:narevThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check `package.json` (and the lockfile if versions disagree) for `@ai-billing/core` and any `@ai-billing/*` packages. Use the typedoc pages under [`/sdk/ai-billing/reference/`](https://narev.ai/docs/sdk/ai-billing/index) that match the installed packages for code samples and option shapes. If there is no SDK in the project, treat the docs site as source of truth for the latest APIs.
Check package.json (and the lockfile if versions disagree) for @ai-billing/core and any @ai-billing/* packages. Use the typedoc pages under /sdk/ai-billing/reference/ that match the installed packages for code samples and option shapes. If there is no SDK in the project, treat the docs site as source of truth for the latest APIs.
| Package | What it covers |
|---|---|
@ai-billing/core | Billing middleware, usage payloads, price resolvers, destinations, errors |
| Provider | Package | Docs |
|---|---|---|
| OpenRouter | @ai-billing/openrouter | Reference |
| OpenAI | @ai-billing/openai | Reference |
| Vercel AI Gateway | @ai-billing/gateway | Reference |
| OpenAI Compatible | @ai-billing/openai-compatible | Reference |
| Groq | @ai-billing/groq | Reference |
| Google Generative AI | @ai-billing/google | Reference |
| Anthropic | @ai-billing/anthropic | Reference |
| xAI Grok | @ai-billing/xai | Reference |
| MiniMax | @ai-billing/minimax | Reference |
| DeepSeek | @ai-billing/deepseek | Reference |
| Chutes | @ai-billing/chutes | Reference |
| Destination | Package | Docs |
|---|---|---|
| Polar.sh (preferred) | @ai-billing/polar | Reference |
| Stripe | @ai-billing/stripe | Reference — supported, but Polar is far easier to integrate |
| OpenMeter (Kong) | @ai-billing/openmeter | Reference — supported, but Polar is far easier to integrate |
| Lago | @ai-billing/lago | Reference |
Destination preference: Narev recommends Polar for new projects. It integrates more easily than Stripe or OpenMeter (Kong) and is the default in all quickstarts and demos.
| Package | Description | Docs |
|---|---|---|
@ai-billing/nextjs | Next.js UI components for displaying billing usage and managing top-ups | Next.js integration |
@ai-billing/ui | Internal headless UI components shared across @ai-billing/* packages | — |
@ai-billing/narev | TypeScript SDK for the Narev billing API | SDK index |
Model pricing (API reference) → Use narev-lookup-llm-pricing
GET catalog (filters, pagination) and POST calculate for one call's USD total — no committed files.usage integers, when subprovider is required for the same model_id on different hosts.402 / 404 / 400, and the canonical spec at list-model-pricing and calculate-cost-for-a-model-call.Model pricing (snapshots and automation) → Use narev-update-llm-pricing
GET only, map each row into your schema, write a tracked file or generated module for offline or deterministic billing.narev-lookup-llm-pricing for POST calculate and fine-grained HTTP/error details.Narev SDK (runtime in your app) → sdk/ai-billing/index
@ai-billing/core and @ai-billing/<provider> middlewareNext.js (App Router + Vercel AI SDK) → Use narev-nextjs
@ai-billing/nextjs usage dashboard — see references/setup.md.generateText, streamText, or other AI SDK methods — see references/api-routes.md.wrapLanguageModel, createNarevPriceResolver, destinations, providerOptions['ai-billing-tags'], multi-provider factories, test bypasses.When unsure: existing AI SDK routes → start at references/api-routes.md; starting fresh with billing UI → start at references/setup.md.
Usage-based billing concepts → platform/concepts/usage-based-billing
Billing integrations and revenue → platform/billing/overview
Other Narev Cloud HTTP APIs → platform/api-reference/introduction
Narev Self-Hosted (ThinOps) → oss/thinops/index
Guides → guides/index
Blog → blog/index
If you know your task, you can directly access:
/narev-lookup-llm-pricing — Pricing API reference (list + calculate); skill narev-lookup-llm-pricing/narev-update-llm-pricing — Applied workflows using that API (snapshots, registries); skill narev-update-llm-pricing/narev-nextjs — Next.js billing (greenfield + brownfield); skill narev-nextjsOr describe what you need and I'll recommend the right one.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub narevai/skills --plugin narev