Build

Build with Yalango

Use Yalango as the brain for language learning experiences you build. Keep decks, vocabulary and spaced repetition in Yalango - feed words in and read what is due from a script or an AI assistant.

The brain

Yalango keeps the hard parts

You build the experience around it - a script, a bot, a custom study flow. Yalango stores the decks, tracks vocabulary and schedules reviews.

Decks and cards

Create private decks, add or edit up to 100 cards at a time, and manage custom fields from a script or an assistant.

Shared vocabulary

Look a word up across everything you study before you add it again - vocabulary is shared, so duplicates show up twice in every review.

Spaced repetition

Cards you add enter the same review queue as cards from the web app. Read what is overdue, due today and coming up - the schedule stays in Yalango.

Pronunciation and pinyin

Cards added through the API or MCP get pronunciation audio and pinyin the same way cards added in the app do. You do not generate those yourself.

Two ways in

REST API or MCP - same capabilities

Pick the interface that fits how you work. Both use the same scopes and the same API key when you authenticate with a key.

REST API

Scripts, servers, local tools

Base URL https://yalango.com/api/v1. Bearer token in the Authorization header. OpenAPI at /api/v1/openapi.json.

curl https://yalango.com/api/v1/decks \
  -H "Authorization: Bearer yal_your_key_here"
API documentation

MCP

ChatGPT, Claude, Cursor and more

Endpoint https://yalango.com/mcp. Sign in with OAuth in ChatGPT or Claude, or pass an API key header in Cursor and Claude Code.

{
  "mcpServers": {
    "yalango": {
      "url": "https://yalango.com/mcp",
      "headers": {
        "Authorization": "Bearer yal_your_key_here"
      }
    }
  }
}
Connect an AI assistant
Example builds

What people build on top

Three starting points - a script that collects words, an assistant that edits your decks, or a dashboard that shows what is due.

Save words from a script

Scrape a reading list, parse a subtitle file, or pull terms from a notebook - then POST them into a deck in batches of up to 100.

Ask an assistant to build a deck

Connect ChatGPT, Claude or Cursor over MCP and say "add these words from the article to my Spanish deck" - it calls the tools in your account.

Show what is due

Hit the review endpoint or ask an assistant for a summary - overdue, due today, unstarted and a short forecast - without opening the app.

Good to know

Honest limits

  • Works on your own account only. You need a verified email. Premium is not required, but free plan limits on decks and cards still apply.

  • The REST API has no CORS headers - call it from a server, a terminal or a local script, never from front-end JavaScript in a browser.

  • Vocabulary lookup and the review queue are read-only. You can see what is due; the schedule itself stays inside Yalango.

  • Deleting decks, and tables, are not available through the API yet. Cards and custom fields can be deleted.

FAQ

Frequently asked questions

Do I need Premium to use the API or MCP?

No. Every signed-in account with a verified email can create API keys and connect assistants. Free plan limits on decks and cards still apply.

What is the difference between the API and MCP?

They reach the same capabilities. The REST API is for scripts and backends you write yourself. MCP is for AI assistants like ChatGPT, Claude and Cursor - you ask in plain language and the assistant calls the tools.

Can I call the API from a browser app?

No. The API sends no CORS headers on purpose, so a key used on a web page would be visible to everyone who loads it. Call it from a server, a terminal or a local script.

Where do I create an API key?

In Settings under API. You pick a name, choose scopes and copy the key once - it is only shown at creation time. The same key works for the REST API and for MCP clients that use a header.

Which AI assistants work with Yalango?

Any client that speaks MCP over streamable HTTP. ChatGPT and Claude can sign in with OAuth. Cursor and Claude Code use an API key in a header. Other clients can use either path.

Is there an OpenAPI schema?

Yes. An OpenAPI 3.1 description of every endpoint is at https://yalango.com/api/v1/openapi.json. It needs no API key and can be fed to a client generator.

Looking for something else? Browse all use cases or open the API docs.

Start building with Yalango

Free account. Create an API key in settings and point your script or assistant at it.