Skip to content
API status
Console guide

Credits and usage

Buy API credits, check consumption, and set a low-balance warning.

Open Credits in the bottom dock, or click Buy Credits on the overview. In the current Console, this page requires an Owner or Finance role.

Item What it is for Where you manage it
API credits Prepaid usage for authenticated Management API requests. Credits
Server license Entitlement to connect a server with the selected account capacity. Servers
Market subscription Access to a market package for the organization. Markets
Trading account balance The ledger balance of a specific trading account, in its server’s currency. Server Accounts or Finance

Buying credits does not increase a trading account balance, buy a server license, or renew a market subscription.

  1. Choose a package

    Under Purchase Credits, review each package’s credit quantity and price. Click Buy beside the package you want.

  2. Complete payment

    Follow the Pay with crypto dialog. Choose the network and asset, verify the receiving address and amount, then submit the transaction hash. See Payments and purchase history.

  3. Wait for confirmation

    A submitted payment must be confirmed by a Koneth administrator. Check Purchase History, then revisit Credits to confirm that Balance has increased before relying on the new credits.

Package sizes and prices are configurable. Use the current values shown in Console rather than a price quoted in an older guide.

If the catalog cannot load, use Try again. If it shows No packages available, use Refresh packages or ask your Koneth contact about availability.

  1. Find Settings on the Credits page.
  2. Enter a nonnegative whole number in Low Balance Threshold.
  3. Click Save and confirm Threshold updated.

The Balance card shows a low-balance warning when your balance falls below that threshold. Choose a threshold that leaves enough time to buy credits and obtain payment approval.

Used This Period shows recorded usage. Usage Breakdown groups consumed credits by operation.

The current page does not offer a date-range selector and requests usage without a starting date. Treat this total as available recorded usage, not a guaranteed monthly billing total.

For integrations, each authenticated Management API request consumes the configured request price. Polling for a command result also consumes credits, and an authenticated request may be charged even if it later fails validation. See API credits for the detailed charging rules.

Keep polling and retries bounded, and monitor the balance before it reaches zero. Creating an API key alone does not add credits.