Сбер API MCP: Documentation
Updated:
Connection
Not self-service: access requires a Sber API agreement (the "Companies" set: "Payment orders" + "Statements"). Steps: register at api.developer.sber.ru and sign a bank agreement (your organization gets a MemberID) → get a TLS certificate for the secure channel → obtain an OAuth2 access_token for a SberBusiness ID user, scoped to MCP_COMMON + MCP_PAYMENT/MCP_STATEMENT.
Addresses (test/production): payments — .../fintech/api/business-payments/mcp, statements — .../fintech/api/statement/mcp, on hosts iftfintech.testsbi.sberbank.ru:9443 and fintech.sberbank.ru:9443.
Tools
correspondent_rur.get— look up a counterparty by TIN/OGRN/name: details and ruble accounts.rur_payment.create_invoice— draft a ruble payment from free-form details; the LLM generates theexternalId.rur_payment.get_state— status byexternalId(IMPLEMENTED,REQUISITEERROR, etc.), max 5 calls/sec.statement.get_summary— account turnover and balances for a day.statement.get_rur_transactions— statement entries for a date, paginated.statement.get_rur_increment— turnover for the current operating day from a given time.
Statements cover the past 5 years plus the current year.
Agent flow
"Create a payment order for Romashka LLC for 100,000 RUB for services under contract 111, VAT 20%", "show the day totals for this account on 2025-03-04", "check the status of the payment with externalId ...".
Limits
A draft isn't an executed payment — nothing moves without a signature in SberBusiness; the agent should confirm the details with the user before submitting. There is no public self-service endpoint.
Pricing
Connecting to and using Sber API is free; you need a SberBusiness settlement agreement — account operations are billed at standard cash-management rates. Unveiled at SPIEF 2026 as the backbone of the "Business Assistant" AI, full rollout planned for autumn 2026.