Is Russian e-commerce and fintech ready for AI agents? A review of 424 market products / Habr

Finding a product, building a cart, and making a purchase are different capabilities

Lenta: retrieve information. The API provides stores, products, prices, and availability. Authorization is not required. Order checkout and payment are not confirmed in the published set.

VkusVill: prepare a purchase. The vkusvill_cart_link_create method is responsible for the cart link. Authorized users have access to order history and personalized offers. I did not find any methods for placing an order or debiting funds in the published set.

Business Lines: create a shipping request. The API allows you to create a request and request changes. For example, canceling a delivery from or to an address requires verification and may be rejected. A payment link does not necessarily mean that a payment has been made.

Search is supported by 53 integrations. Payment is supported by 5.

For this subset, I selected 59 integrations: 50 with a primary personal purpose and another 9 with an additional personal use case.

Search is supported by 53 integrations, order creation or confirmation by 8, and payment transactions by 5. These are different personal use cases, not just shopping. Search also includes files, emails, and financial data.A single connection can support multiple stages: this is capability coverage, not a funnel.

Of the five payment capabilities, four relate to third-party MCPs and one to the official YuMoney API. These are not five stores with ready-made purchasing through an agent.

The most connections are in fintech and store automation

In fintech, connections were found in 48 of 56 services, and in store and customer management in 46 of 65.

For comparison: 9 of 19 entertainment services and 4 of 9 home services have connections.This indicates the availability of a published way to connect, not a percentage of readiness for a personal agent. Access may be partner-only.

The map below includes all 424 services. To check a specific connection, it is easier to use the registry of services, capabilities, and access conditions.

Open the map full-size.

The seller has an API. But the buyer has not been invited yet

Through the Ozon Seller API, you can manage products, prices, and shipments. But I need a buyer agent. The availability of the Seller API does not enable it to place an order in my account.

Here, B2B and B2C indicate the intended purpose of the service: for companies and individual entrepreneurs, or for individuals. They do not indicate API access rights.I also classified another 29 integrations under data and development.

For 17 of the 50 personal integrations, official self-service access is available. These are 14 services, including the public MCP tools for VkusVilla, the Lens catalog API, Yandex Disk, and Smart Home.

Self-service access means no mandatory corporate contract or paid connection plan. An account, a brokerage account, identity verification, OAuth, and application setup may be required. The other 33 integrations have additional requirements, or the access process is unclear.

Difficulties begin even before the first request

Across the entire sample, there are 28 integrations with official self-service access, including 17 personal ones. The remaining 284 require additional conditions or clarification of access.

For 191 integrations, corporate access, a seller account, or a partner role is required. In 80 cases, approval, special permission, or administrator setup is required. Paid access and running on your own server are also possible. The requirements overlap.

An audience threshold is noted for the Aviasales Search API and the MCP that depends on it. It applies to obtaining your own access to Search API, and does not automatically apply to users of someone else’s hosted MCP or other API services.

I did not treat the cost of the goods, delivery, or transaction commissions as a connection fee. OAuth itself does not imply restricted access.It is important whether the user can obtain the permissions for their task.

There are many actions, but most remain within digital services

The assumption that most APIs only read information was not confirmed. Based on the documented capabilities, I divided the 312 integrations into five groups:

• For 77, only information retrieval was confirmed: search, comparison, reading, and calculation.

• 8 prepare a shopping cart, a draft, or a link for continuation.

• TAG163@@186 allow digital data to be changed: send a message, publish a post, or edit a record.

• 34 allow a product order, delivery, or reservation to be arranged, or a command to be sent to a device.

• For 7, there was not enough information.

I did not count search as an action. Uploading a file via the Yandex Disk API is already a digital action with a verifiable result. The Yandex Smart Home API allows a command to be sent to a device or a scenario to be launched. A physical result is possible here without any purchase at all.

Among integrations whose primary purpose is personal tasks, such actions are provided by 10 integrations across 9 services.Yandex Smart Home is counted twice: the API and a third-party MCP.

Five MCPs were created by third-party developers. Four use internal APIs or browser automation; the Smart Home MCP uses the official API. The authors of the Pyaterochka MCP explicitly describe reconstructing requests based on how the web client works. However, it is incorrect to characterize all third-party MCPs as the result of reverse engineering.

The table lists the capabilities described in the documentation. A created order does not yet mean that the goods have been delivered, and statements by MCP authors do not constitute commitments by the service owner.