Usage & BYOK
Credit balance, the live consumption ledger, and where you bring your own LLM keys to bypass credit billing.
The Usage page is the live financial console for your guild. It has two tabs:
- Usage — current credit balance + a transaction-level activity feed
- BYOK — register your own LLM provider keys to bypass credits
The Usage tab
Credit balance at the top: total credits + EUR equivalent + the rate
(1 EUR = 100 credits). The Add credits button takes you straight to
Stripe checkout for a top-up.
The activity feed is the ledger: every LLM call, image generation, TTS render, workflow run produces a row. Columns: When (relative timestamp), Kind (provider), Billing (BYOK / PENDING / SHARED-KEY), Model · usage (tokens or other unit), Credits (how many credits this row consumed, "—" for BYOK).
Filter tabs: ALL · CREDITS · BYOK · PENDING. PENDING is a row that's been recorded but the billing engine hasn't reconciled yet — these resolve within a few hours.
The BYOK tab
Three sections:
1. LLM Provider Keys — first-class providers Guilde supports directly. Anthropic, OpenAI, Google Gemini, OpenRouter, Mistral, Groq. For each: paste an API key, generations route through your account, the calls are not billed against Guilde credits.
2. Shared-key providers — fungible inference services where Guilde
can call on your guild's behalf and debit credits (Replicate, ElevenLabs,
…). Toggle "Enable shared-key fallback" to let Guilde supply the key (and
charge credits at the listed rate, e.g. ~500 mC/image). Or paste your
own key to bypass.
3. Subscription credentials — OAuth tokens that let agent CLIs use
your existing third-party subscriptions instead of paid API access. E.g.
the long-lived claude-code-oauth token uses your Claude.ai Pro/Max
plan when the claude CLI runs in your operator's sandbox.
Where keys actually live
Keys you add from the BYOK tab are stored in the Secrets vault — encrypted, never visible in plaintext to operators, scoped to this guild (or to org-level via Org settings).
The BYOK tab is just a curated front end onto the secrets vault that knows which slug each provider expects.
Per-guild vs org-wide BYOK
You have two scopes:
- Per-guild (this page) — keys apply to operators inside this guild only.
- Org-wide (Org settings → Connectors) — keys inherited by every guild in the org. Useful for paying centrally instead of per-guild.
Per-guild wins over org-wide when both are set, so you can override the org default for a specific guild.
What's next
- Billing — plans, monthly grants, Stripe
- Secrets — the vault behind BYOK
- BYOK tutorial — walk-through with screenshots
- Operators — where to pick which model an operator uses (the guild-default LLM picker lives there)