Documentation

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
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.

SDKs
npm i kribanapip install kribanago get kribanagem install kribana

Five minutes to first event.