Skip to the page
Lymidocs

Start

Lymi docs

Lymi keeps the cards you are learning and asks you about them again at the right time. An assistant or a script can do anything you do by hand, over the same API the app uses.

Add a card once, wherever you meet it. Lymi keeps it and brings it back before you forget.

Two ways in

Pick by who is calling. An assistant such as Claude or ChatGPT signs in as you, over OAuth, and never sees a key. A script you wrote uses an API key.

MCP
An assistant connects to /mcp and asks you to sign in once. Best for “add these five cards to my Italian deck” in the middle of a conversation.
API key
A header on every request, made in Settings. Best for curl, cron jobs, a shortcut on your phone, and anything you run yourself.

The API has its own origin

The guides live on the public website, while the API and MCP server stay with the product. There is no version in the path.

Base URL
https://my.lymi.app

The machine-readable description of every route lives at https://my.lymi.app/api/openapi.json. The API reference is that document, rendered.

What an integration may do

A key or a connected assistant can read your decks and cards, add and edit them, and archive or restore them. Three things are yours alone, from the app, whatever the scope:

  • Grading a review. Only you can say whether you remembered a card.
  • Managing API keys. A key can never mint or revoke another key.
  • Deleting anything. There is no delete. Archiving hides a card and restoring brings it back with its schedule intact.

Where to go next