Uzum
Uzum is an Uzbekistan-based digital ecosystem headquartered in Tashkent that bundles e-commerce, fintech and digital banking into a single group: Uzum Market (the country's largest online marketplace), Uzum Tezkor (rapid food and grocery delivery), Uzum Bank (a licensed digital bank), and Uzum Nasiya (consumer BNPL / installment lending). Its developer-facing API surface is published by Uzum Bank at developer.uzumbank.uz, where nine OpenAPI contracts and a JSON-RPC 2.0 Banking-as-a-Service hub cover card acquiring (Uzum Checkout), QR and cash-register payments (Uzum Fast Pay, Dynamic QR), tax receipt fiscalization to the Uzbek State Tax Committee (Uzum Fiscalization), inbound and outbound cross-border money transfer (Uzum CrossBorder Transfer, Remit Core), installment contract origination (Uzum Nasiya Partner API), in-app merchant billing (Merchant API webhooks) and FX rate quoting (RateKeeper). Uzum Market additionally operates a seller-cabinet API at api-seller.uzum.uz for FBO/FBS order, inventory and price synchronization, which is credential-gated. All Uzum Bank API programs are onboarded through an account manager rather than self-service signup.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Uzum the way a machine reads it — 17 machine-readable artifacts across 11 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 — Uzum scores 52.8/100 (developing), with a separate agent-readiness read of 35/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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-09-02 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Uzum'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/uzum/"
title="Uzum on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/uzum.svg"
alt="Uzum Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/uzum/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/uzum/"
title="Uzum on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/uzum/card.svg"
alt="Uzum 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 Uzum
Each block below is one kind of artifact we hold for Uzum. 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 11
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.
Uzum Checkout
Payment gateway for websites and mobile applications. Card payments (Visa, Mastercard, Uzcard, Humo), one-step and two-step authorization, back-to-back payment without the hoste...
Uzum CrossBorder Transfer
International money transfer between Uzbekistan and other countries. Transfers to Uzbekistan by phone number or card number, transfers from Uzbekistan by card number, cross-bord...
Remit Core
Single integration point for cross-border remittances. Partners register, process, confirm, cancel and status-check CREDIT and DEBIT transfers; Remit Core handles routing, valid...
Uzum Nasiya Partner API
REST API for partner integration with the Uzum Nasiya installment (BNPL) service. Buyer registration through an Uzum Nasiya WebView, buyer status and credit limit checks, basket...
Uzum Fiscalization
Fiscalizes sales and refund receipts and submits them to the Uzbekistan State Tax Committee through a Fiscal Data Operator. Generates receipt links, supports non-fiscal receipts...
Uzum Fast Pay
Instant QR-code payments and payments through cash-register and POS / fiscal register systems, where the seller scans the customer's QR code from the Uzum Bank app. Payment proc...
Uzum Dynamic QR
Dynamic QR payment for a QR code printed on a POS receipt or shown on a cash-register screen, scanned by the customer in the Uzum Bank mobile application. Order creation and pay...
Uzum Merchant API
Webhook protocol that lets partners accept payments from inside the Uzum Bank mobile application. Uzum Bank calls five partner-implemented webhooks — check, create, confirm, rev...
Uzum RateKeeper
Partner-facing foreign-exchange rate service. Converts an amount between currencies at the current Uzum rate and returns the partner's conversion limits. Documented on the Uzum ...
Uzum BaaS Payment Hub
Banking-as-a-Service JSON-RPC 2.0 API that lets partners embed payments, transfers and account and card operations inside Uzbekistan's national payment system. Covers account ba...
Uzum Market Seller API
Seller-cabinet API for Uzum Market used to synchronise marketplace orders, inventory and prices for both Fulfilment by Operator (FBO) and Fulfilment by Seller (FBS) models. Acce...
Scroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Uzum MCP Server
MCP SERVERPricing 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.
Uzum 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.
Uzum Rate Limits
RATE LIMITSEvent Specifications 1
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.
Uzum Merchant Webhooks
ASYNCAPISecurity 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.
Resources
Every other property we hold for Uzum — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/uzum · machine-readable index on apis.io
This is an independent, third-party profile of Uzum, 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.