Billing
How credits and costs work.
Credits
Galadri uses a credit-based billing system. Each API request consumes credits based on the AI model tokens used and the tools invoked. Your credit balance is displayed in the Galadri Console.
Cost Breakdown
Each chat request reports its cost in the usage event (streaming) or usage field (non-streaming). Use cost_micro_usd for the precise credit amount. cost_cents is a rounded rollup for compatibility. The cost includes:
- AI model tokens - Prompt tokens, completion tokens, and thinking tokens at the model's rate (passed through at exact provider cost).
- Capability execution - Per-use costs for external API calls (Google Maps, web search, etc.).
Console Controls
Organization owners and admins can manage billing from the Console:
- Add credits with a saved card. Credit purchases include the displayed processing fee.
- Configure auto top-up so API traffic continues when the balance falls below your threshold.
- Set a monthly card spending cap for automatic top-ups.
- Manage payment methods and fallback card order.
- Set the billing email used for receipts.
- Review transaction history for purchases, auto top-ups, usage, and adjustments.
Insufficient Credits
If your credit balance is zero, the API returns a 402 Payment Required error. Add credits in the Galadri Console to resume API access.
Cost reporting
Use the response-level usage object for per-request costs, and the Console transaction history for account-level billing events. Token costs are passed through at exact provider cost. Provider-backed tools such as image generation, maps, traffic, fuel prices, and vehicle market data are billed at the listed per-tool price. Sales Listings uses the base price for normal inventory lookups and higher bounded tiers when a request inspects a larger pooled inventory set before returning a shortlist.