agentsclimarketplace

Narev starter

Skill narevai/skills/skills/narev-starter

Install
npx -y skills add narevai/skills --skill narev-starter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

9.3 KB, as published. Nobody here has run it

Narev starter

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.

Packages

Core

PackageWhat it covers
@ai-billing/coreBilling middleware, usage payloads, price resolvers, destinations, errors

Provider middleware

ProviderPackageDocs
OpenRouter@ai-billing/openrouterReference
OpenAI@ai-billing/openaiReference
Vercel AI Gateway@ai-billing/gatewayReference
OpenAI Compatible@ai-billing/openai-compatibleReference
Groq@ai-billing/groqReference
Google Generative AI@ai-billing/googleReference
Anthropic@ai-billing/anthropicReference
xAI Grok@ai-billing/xaiReference
MiniMax@ai-billing/minimaxReference
DeepSeek@ai-billing/deepseekReference
Chutes@ai-billing/chutesReference

Billing destinations

DestinationPackageDocs
Polar.sh (preferred)@ai-billing/polarReference
Stripe@ai-billing/stripeReference — supported, but Polar is far easier to integrate
OpenMeter (Kong)@ai-billing/openmeterReference — supported, but Polar is far easier to integrate
Lago@ai-billing/lagoReference

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.

UI & SDKs

PackageDescriptionDocs
@ai-billing/nextjsNext.js UI components for displaying billing usage and managing top-upsNext.js integration
@ai-billing/uiInternal headless UI components shared across @ai-billing/* packages—
@ai-billing/narevTypeScript SDK for the Narev billing APISDK index

By task

Model pricing (API reference) → Use narev-lookup-llm-pricing

  • Pricing API on https://api.narev.ai (public, no Bearer) — seven endpoints only (see lookup skill): reference providers/models, GET /v1/price/{provider_id}, GET /v1/price/search, GET /v1/find/cheapest/{model_id}, POST /v1/calculate.
  • Rates: pricing.prompt / pricing.completion (USD per token). One-call USD: POST /v1/calculate. Do not use legacy POST /models/pricing/calculate or GET /v1/models/pricing.
  • Docs: API introduction, calculate.

Model pricing (snapshots and automation) → Use narev-update-llm-pricing

  • Consumes lookup output: paginate GET /v1/price/search or GET /v1/price/{provider_id}, map pricing.* into your schema, write a tracked file.
  • Implementation choices: merge vs replace, provider/model scope, unit conversion (API per token vs local per-1M), keys for multi-provider models.
  • Ops: idempotent scripts, readable diffs, optional CI or scheduled refresh; use 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> middleware
  • Destinations, price resolvers, usage payloads, errors
  • Prefer this over raw Pricing HTTP when billing runs inside the app

Next.js (App Router + Vercel AI SDK) → Use narev-nextjs-patterns

  • New app: scaffold packages, env, Polar destination, billed model helper, chat route, and @ai-billing/nextjs usage dashboard — see references/setup.md.
  • Existing app: retrofit billing into route handlers that already call generateText, streamText, or other AI SDK methods — see references/api-routes.md.
  • Shared patterns: 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

  • Meters, products, how Narev Cloud fits the model

Billing integrations and revenue → platform/billing/overview

Other Narev Cloud HTTP APIs → platform/api-reference/introduction

  • Applications, custom metrics, pricing endpoints

Narev Self-Hosted (ThinOps) → oss/thinops/index

Guides → guides/index

Blog → blog/index


Quick navigation

If you know your task, you can directly access:

  • /narev-lookup-llm-pricing — Pricing API reference (seven public endpoints); skill narev-lookup-llm-pricing
  • /narev-update-llm-pricing — Applied workflows using that API (snapshots, registries); skill narev-update-llm-pricing
  • /narev-nextjs-patterns — Next.js billing (greenfield + brownfield); skill narev-nextjs-patterns

Or describe what you need and I'll recommend the right one.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.