Pricing and usage accounting

Rate and mode are separate

Shvydko's published rate is $0.042 per million input tokens; output tokens are free. The current service mode appears in the current configuration panel. In preview, requests are free within the quota, even when a rate has been published.

service_mode in the response determines the request's mode. usage.price_per_million_input_usd is the applied rate; in preview it is null and cost_microusd is 0. Top-up availability is separately indicated by billing_enabled.

Calculating a paid request

Actual cost is calculated from usage.input_tokens returned by the model service. The gateway stores money as integer microUSD and rounds each successful paid request up to the next microUSD.

At a rate of 0.042, a request with 1,000 input tokens costs 42 microUSD, or $0.000042. A 49-token request costs 3 microUSD after rounding. These are arithmetic examples, not estimates of your average request size.

cost_microusd = ceil(input_tokens × price_per_million_input_usd)
cost_usd = cost_microusd / 1_000_000

preview: cost_microusd = 0

Reservation before execution

Before a paid request, the gateway reserves the maximum amount based on its reserve_tokens limit. If balance minus active reservations is insufficient, it returns 402 without calling the model.

On success, the actual amount is charged and the rest of the reservation is released. A model error releases the reservation without a charge. For concurrent requests, the available balance accounts for all active reservations.

Because of the reservation, even a short request may need more available funds than its final cost. Compare available balance and reserve, not just the total balance.

Review usage for a period

In Usage, choose a preset period or custom UTC dates: both dates are inclusive, with a maximum of 90 days. Filter API, Playground, or all requests. The chart supports hourly and daily views and includes intervals with no requests.

History shows 100 requests per page. The snapshot stays stable as you page through it; refresh to include new requests. CSV contains all records for the selected period and source, not just the current page. Cost comes from the actual stored accounting for each request—a change to the published rate does not recalculate older records.

Usage exports contain metadata and accounting, not the original text of your context. To reconcile an individual run, use request_id from the API response or evaluation report.

Balance, payments, and documents

When top-ups are enabled, a workspace owner or admin can choose a one-time top-up from $5 to $1,000 and pay on Stripe's secure checkout page. On return, the account checks that specific payment and updates the balance. Credits are added only after the server confirms payment. Simply following a success link does not change the balance.

Billing shows the available balance, reservations, transaction history, and pending top-ups. If a checkout page is still valid, you can resume it from the list. If you were charged but confirmation is delayed, check the status later or contact support; you do not need to pay again.

A receipt is available for a confirmed payment once Stripe can issue it. Payment details can be managed in Stripe; the billing email and organization name can be changed in workspace settings. A refund appears in history and changes the credit balance; if credits have already been spent, the balance may become negative.

Codebridge Technology, Inc. accepts payment for Shvydko API credits through Stripe in US dollars. Unused purchased credits can be refunded on request, including when closing an account; we reconcile the amount against top-ups and actual usage. Email business@codebridge.tech and identify the payment in your history. The refund and billing-error process is described in the terms of service.

A promo code can be redeemed once per workspace in Billing and adds separate free credits. These are spent first and cannot be refunded for cash. A code may have a redemption deadline and a limit on total redemptions.

Auto top-up is available only after the feature is enabled in paid mode. An admin separately agrees to the balance threshold, amount, and UTC monthly cap, and saves a card through Stripe. No charges are initiated in preview. An error or unknown result pauses auto top-up; there is no automatic repeat charge. Disabling it does not cancel an already submitted payment. Creating custom invoices is not supported.