Sokowatch / Wasoko
Sokowatch — rebranded as Wasoko in 2022 — is a pan-African B2B e-commerce and distribution platform serving informal retailers (the mom-and-pop dukas, kiosks, and neighborhood shops that move the majority of fast-moving consumer goods across the continent). Founded in 2016 in Nairobi, Kenya by Daniel Yu, the platform lets small shopkeepers order FMCG inventory via a mobile app or SMS, with free same-day delivery to the shop door, eliminating costly trips to wholesalers. Wasoko layers embedded fintech on top of commerce: buy-now-pay-later inventory credit, working-capital loans for shopkeepers who often lack access to traditional banking, and digital payments. At peak the company operated across Kenya, Tanzania, Uganda, Rwanda, Côte d'Ivoire, Senegal, and the Democratic Republic of the Congo. In December 2023, Wasoko announced a merger with Egyptian B2B peer MaxAB, which closed in August 2024 to form MaxAB-Wasoko, Africa's largest B2B informal-retail network with more than 450,000 merchants across eight countries (combining MaxAB's North African footprint in Egypt and Morocco with Wasoko's Sub-Saharan reach) and roughly 4,000 employees, co-led by Daniel Yu and MaxAB founder Belal El-Megharbel. Post-merger the group exited underperforming markets (Zambia, Uganda, Senegal) and pivoted harder into fintech, where margins exceed core distribution. Wasoko's revenue model is wholesale-to-retail product sales plus fintech (credit, payments) and logistics fees. The platform is operated as a closed retailer-facing app; there is no public developer API, SDK, partner integration program, or open-source release for the commerce, logistics, or fintech surface. The legacy Sokowatch GitHub organization exists but contains only forks of third-party tools (Apache Superset, Fineract CN, Botpress, Kutt, Portainer) used internally, with no first-party libraries or specifications.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Sokowatch / Wasoko the way a machine reads it — 1 machine-readable artifact, 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 — Sokowatch / Wasoko scores 7.4/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Sokowatch / Wasoko
Each block below is one kind of artifact we hold for Sokowatch / Wasoko. 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.
Security Posture 1
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 Sokowatch / Wasoko — 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sokowatch · machine-readable index on apis.io