Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Stori website screenshot

Stori

Stori is a Mexico City–headquartered fintech (operating as a regulated Sociedad Financiera Popular under CNBV and CONDUSEF oversight) on a mission to democratize credit access for the roughly 400 million underbanked consumers in Latin America. Founded in 2019, the company achieved unicorn status in 2022 and has raised over $400M from investors including GGV Capital, General Catalyst, Lightspeed Venture Partners, Goodwater Capital, Source Code Capital, Vision Plus Capital, BAI Capital, Tresalia, and GIC. Stori's flagship product is the Stori Card, an inclusive Visa credit card marketed to first-time borrowers with little or no formal credit history, alongside Stori Black (premium tier), co-branded cards (SHEIN, Farmacias Similares, sports teams), Cuenta+ (a commission-free deposit account advertising up to 15% annual returns), personal loans up to roughly $3,000 MXN-equivalent, and payment services covering bill pay, mobile recharges, and phone-based merchant collection. The platform is delivered exclusively through its iOS and Android mobile apps and serves more than five million Mexican users. Stori has no public developer API, SDK, CLI, webhook surface, or open-source release; its revenue model is interest, interchange, and fee income from consumer credit and deposit products, with operations in Mexico, Colombia, and a U.S. corporate presence in Arlington, Virginia.

human only

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.

Kin Score

API Evangelist profiles Stori 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 — Stori scores 7.7/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 7.7/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Banking & Open Finance 2.0 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Stori

Each block below is one kind of artifact we hold for Stori. 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.

Stori Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for Stori — 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.

Access & Security 1

Authentication, authorization, and security posture

← All providers · Data indexed from github.com/api-evangelist/stori · machine-readable index on apis.io