Credits & Metering

AI and tool usage in FundOS is metered in credits against a single workspace balance. Tool calls are tiered; the conversion is 1 credit = $0.01. Platform licensing itself is an annual enterprise agreement scoped per fund — not published here.

Credit tiers

Every tool belongs to one tier. The tier determines the base cost per call.

Tier	Cost	What it covers
read fast	1 credit	Single-table reads — list deals, list LPs, get pipeline, etc.
read multi	2 credits	Cross-table reads — agent context briefing (spans multiple models)
read compute	5 credits	Compute-heavy reads — pricer, waterfall, covenant check
write	10 credits	Writes that create or mutate records (produce human-approval actions)
ai light	25 credits	Gemini AI calls — VDR analysis, ODD generation, tool catalogue
ai heavy	50 credits	Long-form AI generation — CIM / investment memo drafting

Custom pricing: per-tool overrides and per-client multipliers are negotiated in your agreement and configured by the FundOS team. Contact billing@kela.com.

One workspace wallet

There is exactly one credit balance per workspace. Monthly plan grants (use-or-lose, expire at the next cycle) and top-ups (never expire) both land on it; every metered call — OAuth agent, Bearer API key, or REST — draws from it. OAuth clients do not carry their own balance: a client is bound to its organization at first authorization and bills that workspace from then on. Workspace admins can buy top-up credits from the billing page at kela.com/billing.

Check your balance

curl https://kela.com/api/v1/usage \
  -H "Authorization: Bearer $TOKEN"

Response (credit_balance is the workspace balance; usage is per client):

{
  "credit_balance": 4250,
  "spent_today": 47,
  "spent_this_month": 312,
  "top_tools": [
    {"tool": "fundos_get_agent_context", "calls": 18, "credits": 36},
    {"tool": "fundos_list_deals",        "calls": 31, "credits": 31},
    {"tool": "fundos_vdr_analyze",       "calls": 4,  "credits": 100}
  ]
}

Failed calls are refunded

Credits are deducted before a tool runs. If the tool then fails (upstream error, timeout), the charge is automatically reversed with a refund entry on the ledger — you never keep paying for work that didn't happen.

Human sessions

Credits are only consumed by OAuth token requests — agents and developers calling the API. Human browser sessions using the FundOS UI are not charged credits. They are covered by the platform agreement.

Low-balance webhooks

Register a webhook endpoint and subscribe to credit.low and credit.exhausted events to get proactive alerts before your agent is rate-limited. See the Webhooks page.

Usage traces

Every credit movement is recorded in the credit ledger with the tool name, cost, org, and client. Admins can view per-agent spend breakdowns at /admin/usage-traces.