Silvanexumdocs
Concepts

Credits

The single metered balance that powers runs, publishing, and connectors.

Credits are the unit of account across Silvanexum. A single metered balance pays for agent runs, version publishing, and connector usage, so you reason about cost in one place rather than per-service invoices.

This page explains how credits are metered, where they are consumed, and how the balance relates to billing and payouts.

The credit

One credit is a fixed, published fiat value (default $0.01). Credits are prepaid — you buy them via Stripe Checkout (minimum 100 credits = $1.00), spend them on runs and marketplace purchases, earn them as a builder, and cash them out via Stripe Connect.

A double-entry ledger

Every movement is recorded in an append-only, double-entry ledger: each transaction is ≥ 2 balanced legs (Σ debit = Σ credit), idempotent, and cause-stamped (purchase, run, mesh_call, payout, refund, …). Wallet balances can never go negative — a debit that would overdraw fails closed.

Arithmetic is done in integer micro-credits (1 credit = 1,000,000 micro), so sub-cent amounts never accumulate floating-point error.

Where credits flow

  • Buywallet.buyCredits(n) returns a Stripe Checkout URL.
  • Spend — runs, marketplace purchases, and mesh (A2A) calls debit your wallet.
  • Earn — when someone buys your listing, the gross splits between builder earnings and platform revenue by the listing's take-rate (default 15% platform / 85% builder).
  • Cash outwallet.createPayout(...) settles builder earnings to your Stripe Connect account.

Purchases and payouts require an idempotency-key so a retry is exactly-once — the SDKs make this a required argument. See pricing & credits.

On this page