This is an urgent correction. A CryptoBot payment could succeed while the balance stayed the same. Separately, under heavy load the API sometimes returned an internal error instead of asking the client to try again shortly. Both cases are fixed.
This hotfix follows the October 27 update. It restores top-up buttons and the confirmation shown after activating a paid purchase in the bot. In some cases the action had already been completed, but the bot showed an error or nothing at all.
This hotfix restores buttons on screens the bot shows after you enter text. Previously, a button on a newly displayed screen could incorrectly say that the interface had changed and ask you to reopen the menu.
An urgent hotfix addresses issues when closing support tickets, restores preset top-up amount buttons, enables promo code support for Digiseller, and streamlines model presentation in the Telegram bot.
An urgent hotfix fixes display issues when opening large support tickets in the Telegram bot: conversation threads and status event histories are now divided into manageable pages, preventing Telegram message length limit errors.
An urgent hotfix resolves pricing discrepancies for POST /v1/messages using
Anthropic prompt caching, ensuring complete consistency between API response
usage metrics, public catalog pricing rules, and ledger transaction records.
An urgent hotfix synchronizes model catalog representations across the API, Telegram bot, and documentation: eliminating duplicate model entries across endpoints, consolidating pricing attributes, and enforcing canonical key permission checks.
An urgent correction restores reliable handling for Claude models across
multiple API protocols, brings back access to claude-fable-5, and ensures
strict model catalog synchronization between the API and Telegram bot.