Are Russian e-commerce and fintech ready for AI agents? A review of 424 market products (Готов ли российский e-com и финтех к ИИ-агентам? Обзор 424 рыночных продуктов)
A · Strong evidence A single analyst's desk review of public documentation for 424 Russian services, with stated counting rules and a published registry of connections, access terms and sources, so every count can be checked.
Summary based on the full text·Original: about 6 minutes to read
In short
A 7 November 2026 Habr post by analyst Vika (dochkinavika) asking what a personal AI agent could actually do for an ordinary person in Russia: shop, pay, book delivery or control devices. She reviewed public documentation for 424 companies and products. Connections exist, but mostly for businesses: sellers can manage catalogues through APIs, while buyers have few official ways to let an agent place and pay for an order. Of the five payment capabilities found for personal use, four are third-party MCPs.
Key numbers
- 232 of 424services with at least one documented API, MCP or A2A connection (312 connections in total)
- 214 / 97 / 1API, MCP and A2A connections found; of the MCPs 34 official and 63 third-party
- 233 vs 50connections intended mainly for business versus for personal tasks
- 17 of 50personal-use connections with official self-serve access
- 10personal connections (9 services) that claim a physical result such as an order, transport or device command; half built by third parties
As reported by the source.
Russian·Web page·opens habr.com
What it reports
- 232 services have 312 connections: 214 API, 97 MCP, one A2A (Albato Copilot, partner access only).
- By intended audience: 233 connections mainly for business, 50 for personal tasks, 29 for data and development.
- Only 28 connections in the whole sample have official self-serve access, 17 of them personal (14 services, including the VkusVill MCP, Lenta catalogue API, Yandex Disk and Yandex Smart Home).
- 191 connections need corporate access, a seller account or partner role; 80 need approval, separate admission or admin setup.
- By strongest documented capability: 77 read only, 8 prepare a cart or draft, 186 change digital data, 34 place an order, transport, booking or device command, 7 unclear.
- Of 59 connections with personal scenarios: 53 support search, 8 order creation or confirmation, 5 payment.
- Connections exist at 48 of 56 fintech services and 46 of 65 store-management services, against 9 of 19 in entertainment and 4 of 9 in home services.
- Example: VkusVill's official MCP can build a cart link, but a person must complete the purchase in the app.
How they got it
One registry entry per service-protocol pair, built from official documentation and third-party connector descriptions. Each entry is assigned one main audience and one strongest confirmed result. 192 services lacked open confirmation of a connection. The author did not test whether connections work.
Limits
- Documentation review only; reliability and real-world function are untested.
- "Not confirmed" does not mean absent or forbidden; partner-only access may exist unseen.
- Sample selection is the author's; no claim to cover the whole market.
- Third-party MCP claims are the authors' statements, not service owners' commitments.
Why it matters for companies
For consumer-facing firms the gap is clear: most APIs serve sellers and partners, and few let a customer's own agent search, order, pay and check the result under official terms. Companies planning for agent-driven buying should decide which actions to expose to buyers' agents, with separate read and write rights, explicit confirmation and protection against duplicate orders, the five checks the author lists. Otherwise third-party MCPs built on browser automation will fill the gap without the company's control.
Key passages in translation
Russian original
Главный вывод: в моей выборке подключений для бизнеса заметно больше, чем для личных задач.
The main finding: in my sample there are noticeably more connections for business than for personal tasks.
Russian original
Наличие Seller API не дает ему возможности оформить заказ в моем аккаунте.
Having a Seller API does not let the agent place an order in my account.
Russian original
Из пяти платежных возможностей четыре относятся к сторонним MCP, одна к официальному API ЮMoney.
Of the five payment capabilities, four belong to third-party MCPs and one to YooMoney's official API.
Summary based on the full text. Read the original for the full argument and data.Read the original on habr.com