Billing
One Aporto login can have two independent prepaid wallets. USD is the default. A manager enables the RUB wallet by request. Each wallet has its own balance, API keys, and usage and billing history. There is no subscription charge for API usage.
Live prices
The catalog reads the gateway's current default group tariffs and quota unit. It does not maintain a second hand-written model list. Models with conditional tariffs show their published rate variants rather than one flattened fixed price.
RUB request tariffs
Open current RUB request tariffs →
For supported RUB-wallet requests, each live USD tariff is calculated in RUB by this rule:
RUB debit = published Aporto USD tariff for actual usage × effective CBR USD/RUB rate × 1.40
The CBR rate and the 1.40 multiplier are applied exactly once to the request charge. Their exact product is not rounded up first; only the final money amount is rounded once. Funding the RUB wallet is a separate 1:1 credit and does not use this calculation.
The catalog shows the CBR effective date and the time the rate was checked. Only a fresh, verified, already-effective rate is shown; a missing, stale, future-dated, or invented fallback rate is not used. RUB amounts explain request tariffs and do not mean that every catalog model or endpoint supports the RUB wallet.
Independent wallets
| USD wallet · Default | RUB wallet · By request |
|---|---|
| Works for the published API capabilities | A manager enables it for the account |
| Holds USD and uses API keys linked to the USD wallet | Holds RUB and uses API keys linked to the RUB wallet |
| Keeps its own balance and usage and billing history | Keeps its own balance and usage and billing history |
Open or request the RUB wallet →
The link opens the RUB wallet when it is active, or its request/status view otherwise. It never approves access; manager approval is required.
Contact the manager
The dashboard link above remains the RUB-wallet request/status flow. To ask the manager about activation or a bank invoice, use Email: [email protected] or Telegram: @apitoai_bot. Email opens a draft and Telegram opens the bot; neither contact link submits or approves a wallet request.
Both key types call the same https://api.aporto.tech/v1 endpoint with the same currency-neutral request body. The API key fixes the wallet and billing currency. There is no currency override, automatic conversion, transfer, or fallback charge from the other wallet.
RUB support scope
A RUB key supports text POST /v1/chat/completions, including non-streaming and streaming responses, with ordinary published token tariffs and cache usage. The enabled model set can be narrower than the full catalog. Images, audio, video, realtime, background jobs, and server-executed tools are not supported by the RUB wallet and require a USD key.
Funding the RUB wallet
Funding uses a bank invoice confirmed by a manager; there is no automatic checkout.
- Paying 10,000 RUB credits exactly 10,000 RUB to the RUB wallet.
- No FX conversion or markup is applied to the amount credited.
- Before a supported request is sent upstream, Aporto snapshots the effective CBR rate and the published tariff. That snapshot is used for settlement and any refund. Existing balances and completed history are not revalued when the rate or tariff changes.
- If the RUB wallet cannot cover a request, the USD wallet is not charged as a fallback.
- The USD wallet, its API keys, and its charging behavior remain unchanged.
Legacy RUB invoices for the USD wallet
The compatibility link ?topup=rub still funds the USD wallet under the saved terms of its invoice. It does not select or fund the independent RUB wallet. Existing invoices and completed payments keep their stored accounting amounts.
Usage
Input, output, and cache can have different rates. Use the selected model's live price lines and the wallet's supported scope. Each wallet's own usage history is authoritative for its completed requests.