Know what every AI request costs.
Measure AI usage in real dollars, control runaway AI spending, and connect model costs to customers, features, and revenue.
What VibezCheck Is — and Is Not
- ✓An AI usage metering layer.
- ✓A request-level cost calculator.
- ✓A customer/feature cost attribution layer.
- ✓A spend-control layer.
- ✓A usage-billing bridge.
- ✓A developer-first NPM SDK.
- ✓Eventually, AI unit-economics infrastructure.
- –A generic LLM observability dashboard.
- –A token counter.
- –A logging platform.
- –A prompt database.
- –A Stripe wrapper.
- –A model router.
- –A generic AI monitoring product.
Tokens are useful for engineers. Dollars are useful for businesses.
AI providers bill applications using model-specific usage units such as input tokens, output tokens, cached tokens, and reasoning usage.
Users do not buy tokens.
They buy messages, documents, agent runs, API calls, credits, and subscriptions.
VibezCheck connects the product action to the provider cost.
Measure every AI request in dollars.
Know what an individual request, customer, feature, model, document, or agent session costs.
Calculate provider cost from model usage in-process using BigInt nano-cent rate cards for 700+ models.
Break down prompt, completion, cached, and reasoning usage where supported by the provider response.
Attach customer, organization, feature, and thread identifiers to every request and generation.
Meter streaming responses in real time without routing traffic through an external VibezCheck proxy.
Put a ceiling on AI spending.
Agent workflows can make multiple model and tool calls before a user sees the result. VibezCheck lets developers enforce request-level and session-level spending boundaries.
Stop unusually expensive calls using maxCostPerCallUSD.
Set maximum token ceilings per generation to keep prompt expansion within bounded limits.
Create hard spending ceilings for multi-step agent workflows via sessionBudgetUSD.
Account for external tool execution (web search, sandboxes, code interpreters) inside agent economics.
Connect AI costs to your pricing.
Once your application knows the provider cost of a request, you can use that usage event inside your own pricing and billing system.
Apply a markup multiplier (e.g. 1.30×) to wholesale provider cost to ensure profitable customer retail pricing.
Map usage and dollar consumption directly to customer credits, token pools, or feature quotas.
Emit structured economic usage events asynchronously to Stripe, Metronome, Supabase, or custom queues.
Understand the cost behind every plan, enterprise tenant, product feature, and account in real time.
One line to start metering.
Wrap the model you already use. VibezCheck runs in your application and exposes the usage and cost of the request.
import { streamText } from 'ai';
import { openai } from '@ai-sdk/openai';
import { vibezcheck } from 'vibezcheck';
const result = streamText({
model: vibezcheck(openai('gpt-4o-mini'), {
customer: 'user_123',
maxCostPerCallUSD: 0.50,
}),
prompt: 'Summarize quantum computing in three sentences.',
});Your application already knows the response. Now let it know the cost.
const result = await generateText({
model: openai('gpt-4o-mini'),
prompt,
});
// You have the response.
// What did it cost?
// Which customer generated it?
// Did an agent exceed its budget?const result = await generateText({
model: vibezcheck(openai('gpt-4o-mini'), {
customer: user.id,
maxCostPerCallUSD: 0.50,
}),
prompt,
});
// Real dollar cost calculated.
// Attributed to customer.
// Hard ceiling enforced.Built for Production Engineering
Technical specifications designed for zero risk and clean integration
Frequently Asked Questions
Direct, verifiable answers to common technical and economic questions.
Know the cost before it becomes the bill.
Add AI cost metering to the stack you already use.