Your learning data is yours to build with.

Vocapi is built for learners — including learners who script, chart, and tinker. Alongside the app, Vocapi ships a read-only developer API and an MCP connector, so your own tools and AI tutors can see your real progress.

Built to be understood, not just used.

The two surfaces

A personal, read-only API

  • Predictable resources with cursor-based pagination
  • Personal access tokens created inside the app (Settings → Developer)
  • Scoped, revocable, and hashed at rest
  • Your own data only — cards, reviews, vocabulary strength, progress, free-writing history, and course content your plan can read
Read the API reference

An MCP connector for AI tutors

  • Connect your own Claude (or any MCP client) with your Vocapi sign-in via OAuth
  • The tutor gets a compact briefing of where you are — due reviews, struggling words and why, your usable-vocabulary envelope
  • Plus real lesson and reader content, so it teaches from your actual course instead of guessing

Principles

These hold for both surfaces, and for anything added to them later.

  1. 01

    Read-only by design

    Tools can inspect learning data without changing a learner's progress.

  2. 02

    Learner-self only

    A token or connected tutor sees your data, never anyone else's.

  3. 03

    Explicit responses

    Access boundaries and filtered results are represented in the response.

  4. 04

    Same rules as the app

    The API and tutors see exactly what the app would show you; entitlements are enforced in one shared layer.

Curious to build with your own data?

Start with the versioned API reference, then create a scoped personal key inside Vocapi.

Read the API reference