Sber ID / SberCloud
Sber ID / SberCloud is the cloud computing and AI platform of Sberbank, offering a broad portfolio of IaaS and PaaS services such as virtual machines, managed Kubernetes, object storage, databases, and AI tools. Hosted on Tier III data centres in Russia, the platform complies with Russian federal regulations (152‑FZ, 187‑FZ) and provides SLA‑backed availability. It serves enterprises and developers through a public portal, documentation, pricing tables, and a self‑service console for registration and account management.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Sber ID / SberCloud the way a machine reads it — 33 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sber ID / SberCloud scores 36.5/100 (thin), with a separate agent-readiness read of 23/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
The public developer documentation does not provide any OpenAPI, AsyncAPI, GraphQL, or other machine‑readable contract.
The documentation is public — a person can read it, but a machine cannot. This one is Sber ID / SberCloud's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://cloud.ru/openapi.json→ HTTP 404
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from Sber ID / SberCloud's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/sber/"
title="Sber ID / SberCloud on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/sber.svg"
alt="Sber ID / SberCloud Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/sber/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/sber/"
title="Sber ID / SberCloud on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/sber/card.svg"
alt="Sber ID / SberCloud Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Sber ID / SberCloud
Each block below is one kind of artifact we hold for Sber ID / SberCloud. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Sber API
Public API documentation for Sber services, listed on the Sber Developers portal.
Sber ID / SberCloud Acceptance Advances API
The Acceptance Advances API from Sber ID / SberCloud — 3 operation(s) for acceptance advances.
Sber ID / SberCloud Auth API
The Auth API from Sber ID / SberCloud — 2 operation(s) for auth.
Sber ID / SberCloud Balance API
The Balance API from Sber ID / SberCloud — 1 operation(s) for balance.
Sber ID / SberCloud Client Info API
The Client Info API from Sber ID / SberCloud — 1 operation(s) for client info.
Sber ID / SberCloud Embeddings API
The Embeddings API from Sber ID / SberCloud — 1 operation(s) for embeddings.
Sber ID / SberCloud Files API
The Files API from Sber ID / SberCloud — 4 operation(s) for files.
Sber ID / SberCloud Generic Letters API
The Generic Letters API from Sber ID / SberCloud — 1 operation(s) for generic letters.
Sber ID / SberCloud Ic API
The Ic API from Sber ID / SberCloud — 1 operation(s) for ic.
Sber ID / SberCloud Models API
The Models API from Sber ID / SberCloud — 2 operation(s) for models.
Sber ID / SberCloud OAuth API
The Oauth API from Sber ID / SberCloud — 2 operation(s) for oauth.
Sber ID / SberCloud Payment Requests API
The Payment Requests API from Sber ID / SberCloud — 2 operation(s) for payment requests.
Sber ID / SberCloud Payments API
The Payments API from Sber ID / SberCloud — 5 operation(s) for payments.
Sber ID / SberCloud Placement API
The Placement API from Sber ID / SberCloud — 10 operation(s) for placement.
Sber ID / SberCloud Room API
The Room API from Sber ID / SberCloud — 1 operation(s) for room.
Sber ID / SberCloud Sber ID / SberCloud API
The Sber ID / SberCloud API API from Sber ID / SberCloud — 1 operation(s) for sber id / sbercloud api.
Sber ID / SberCloud Tokens API
The Tokens API from Sber ID / SberCloud — 1 operation(s) for tokens.
Sber ID / SberCloud Chat Completions API
The Chat Completions API from Sber ID / SberCloud — 2 operation(s) for chat completions.
Scroll within the panel for all 18 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Sber Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Sber Rate Limits
RATE LIMITSEvent Specifications 2
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Sber ID AsyncAPI placeholder
This file originally contained HTML content from the Sber partners site. No AsyncAPI specification is published by the provider. The original document included numerous URLs suc...
ASYNCAPISber ID AsyncAPI placeholder
This file originally contained HTML content from the Sber partners site. No AsyncAPI specification is published by the provider. The original document included numerous URLs suc...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Sber Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Sber ID / SberCloud API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
PostAuthLoginRequest
JSON SCHEMAPostChatCompletionsRequest
JSON SCHEMAPostChatCompletionsResponse
JSON SCHEMAPostEmbeddingsRequest
JSON SCHEMAPostFilesRequest
JSON SCHEMAPostV2ChatCompletionsRequest
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Sber ID / SberCloud — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sber · machine-readable index on apis.io
This is an independent, third-party profile of Sber ID / SberCloud, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.