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
Babbel website screenshot

Babbel

Babbel is a Berlin, Germany-based language learning company founded in 2007 by Thomas Holl, Markus Witte, Lorenz Heine, and Toine Diepstraten. It operates one of the world's first online language-learning platforms, offering structured, conversation-focused courses in 14 languages including Spanish, French, German, Italian, Portuguese, Russian, Polish, Swedish, Norwegian, Danish, Dutch, Turkish, Indonesian, and English. The Babbel product suite includes the core subscription Babbel App with interactive bite-sized lessons, speech recognition, and AI conversation partners; Babbel Live for online classes with certified teachers; Babbel for Business for enterprise language training; Babbel Podcasts and Babbel Magazine for supplemental content; and Babbel Videos on YouTube. The company has sold over 25 million subscriptions and reports that 92% of users improved their proficiency in two months, with effectiveness studies conducted by Michigan State University, Yale University, and CUNY. Babbel maintains an additional office in New York City and is privately held. Babbel's revenue model is direct-to-consumer subscriptions (monthly, annual, lifetime tiers) plus enterprise B2B licensing through Babbel for Business; there is no public developer API, SDK, or open-source learner content. The Babbel GitHub organization publishes internal infrastructure tooling (Terraform AWS modules, Puma plugins, OkHttp AWS signing, GitHub Actions) but no consumer-facing API.

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 Babbel 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 — Babbel scores 10.8/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 — 10.8/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 2.1 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
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 Babbel

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

Babbel Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

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

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

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