AntiMalware•October 26, 2026•🇷🇺Translated from Russian

The Real Costs of Using Claude and GPT for Russian Businesses Exposed

Connecting generative AI models has proven simpler than determining their actual financial impact on a company. The base price of tokens is quickly augmented by intermediary fees, exchange rates set by resellers, and applicable taxes, while paid reasoning processes can substantially inflate the final bill. A short AI response does not necessarily translate into a short invoice.

Founder of the Heli service Vitaly Nagay examined both the direct expenses and organizational risks associated with Russian companies accessing overseas models such as Claude and GPT. The author operates in this market and openly states his interest in the topic.

In the provided case study, a support team generates 20,000 requests per month. Considering only the visible output yields an estimated cost of $240. When reasoning tokens are factored in, the total rises to $480. Subsequent adjustments come from payment terms and the chosen intermediary.

To compare suppliers fairly, Nagay suggests calculating the effective exchange rate by dividing the ruble amount charged per request by its official dollar price from the model developer. Internal credits and attractive pricing tables lose their ability to conceal overpayments under this method.

A separate challenge is control and compliance. Personal employee subscriptions raise questions regarding documentation, handling of work-related data, and retention of conversation history. While a Russian intermediary may simplify billing, it does not remove restrictions imposed by the foreign provider.

Before making a purchase, the author recommends verifying detailed billing records, contractual documents, data retention policies, and refund conditions for unused balances. Organizations should also issue separate API keys with spending limits, as automated scripts can rapidly consume allocated budgets.

Related articles

Habr•Other

How a Personal Site Counts Bots Without Storing Any IPs: Pure PHP, No Database, Strict CSP and 160 Tests

A personal website built entirely in pure PHP without frameworks or databases demonstrates advanced defensive security practices while tracking bot activity from an SSH honeypot. The site stores all content in a single JSON file with atomic writes and automatic backups, eliminating database-related attack surfaces and simplifying deployment to folder copying. Strict Content-Security-Policy rules prohibit inline styles and scripts without nonces, forcing the use of SVG attributes, CSSOM updates, and JSON data blocks instead of direct attribute injection. Over 160 automated tests written in PHP attack the site with XSS payloads, CSRF attempts, path traversals, and malformed Markdown to verify that no malicious output reaches the browser. Bot identification relies on behavioral signatures derived from the first twelve cleaned commands of each session, combined with HASSH fingerprints and activity patterns, allowing the site to report unique bot families and address counts without ever publishing IPs. Additional browser-based tests using Chromium validate accessibility, performance budgets, and CSP compliance across desktop and mobile viewports. The entire system runs with zero external dependencies and integrates tests directly into the deployment pipeline.

AntiMalware•Other

Russian Finance Ministry Seeks Central Bank Reports on Systematic P2P Transfers to Tax Authorities

The Russian Ministry of Finance has proposed amendments requiring the Central Bank to share data with the Federal Tax Service on individuals whose bank accounts show signs of regular income received from other private citizens. The changes target article 85 of the Tax Code and form part of the budget package bill numbered 617-9. Under the new rules, the Central Bank would identify such citizens through transaction analysis and transmit the information according to a future agreement with the tax service. The Federal Tax Service would also gain expanded powers to request bank statements from non-entrepreneurs without needing prior debt collection or audit triggers. If approved, the provisions would take effect on 1 January 2027 and apply to operations conducted after 1 January 2026. Separate bills under discussion would impose monthly transfer limits of 30,000 rubles on suspected clients starting in 2028 and require the tax service to notify the Central Bank about account openings and income categories.

安全客•Other

Baidu Launches Ciyuan Exchange to Establish Trust Standards for AI Model Trading

Baidu Intelligent Cloud has introduced the Ciyuan Exchange, a dedicated trading platform for large AI models that aims to solve quality verification and credit issues in an increasingly crowded market. The platform, unveiled at the Baidu World 2026 Conference, already hosts over 100 supply resources with daily calls exceeding 50 million and daily token usage surpassing 700 billion. Founder Li Yanhong positioned the exchange as an infrastructure layer that moves beyond simple model aggregation toward verifiable identity, ongoing performance monitoring, and supplier credit records. The initiative addresses real procurement risks where identical models from different providers show up to twofold differences in throughput and reliability, according to a China Academy of Information and Communications Technology report. By combining model fingerprinting, capability testing, periodic audits, and continuous credit scoring, the platform seeks to create transparent market mechanisms similar to commodity exchanges. This development signals a broader industry shift from raw model capability competition toward standardized service quality, pricing transparency, and reliable delivery infrastructure.

Habr•Other

Windows and MacBook Pro Setup Combines Local Network Access with Dual VPNs and Kill Switch Protection

A user detailed how they integrated an older MacBook Pro into an existing Windows workstation environment while preserving separate user accounts, file sharing, and independent VPN connections. The setup required careful routing configuration to keep the Kill Switch active on both Amnezia VLESS and AmneziaWG without breaking local SMB connectivity. After initial failures caused by the Windows Kill Switch blocking the 192.168.1.0/24 subnet, split tunneling was implemented to route local traffic directly. Separate macOS accounts were created for daily use and a dedicated “Serverok” account for remote scripting and compute tasks. SSH and SFTP ultimately replaced problematic SMB shares for the secondary account, enabling reliable file transfers at over 50 MB/s. The configuration allows simultaneous or sequential use of both machines while maintaining strong VPN protection on each.