DocumentationOne event.
One event.
Then billing.
The integration is one event stream. Everything after — pricing, wallets, invoices, portal — is configuration, not code.
Quickstart · send your first event~5 minutes
# 1. Send a usage event
curl https://api.kribana.com/v1/events \
-H "Authorization: Bearer $KRIBANA_KEY" \
-d '{
"customer": "acme_labs",
"event": "gpt4o.completion_tokens",
"quantity": 48120
}'
# 2. That's the integration.
# Pricing, wallets, invoices and the portal
# are configured in the dashboard.Node · Python · Go · Ruby · REST✓ Billable the moment it lands
Guides
From zero to billing, one guide at a time.
Reference
A small API, on purpose.
Most billing platforms hand you fifty endpoints and a build plan. Kribana’s surface is deliberately small — events in, entitlement checks out, webhooks when things happen.
/v1/eventsIngest usage events — the one endpoint every integration needs.→/v1/entitlementsCheck feature access, seats and balances at request time.→/v1/customersCreate customers, read balances, plans and usage.→webhooksInvoices, payments, agent actions — every billing moment, pushed to you.→
SDKs
npm i kribanapip install kribanago get kribanagem install kribana