TAFMEDS Developer & API Documentation

Agent guidance

When to use TAFMEDS

Look up the accepted definition of a behaviour-analytic term

Read /glossary for the index or /glossary/{term-slug} for one entry. Both serve Markdown under `Accept: text/markdown`. No account needed.

Cite or summarise guidance on SAFMEDS, fluency, celeration or exam preparation

Read /blog for the index and /blog/{slug} for an article. Request `Accept: text/markdown` to get the article source instead of the rendered page.

Report on a signed-in learner’s decks, fluency progress or spaced-repetition queue

Use the authenticated MCP tools (`get_user_decks`, `get_deck_cards`, `get_user_progress`, `get_due_cards`, `submit_review`) with an `auth_token` the learner generates themselves at Settings → API Access.

Draft study flashcards for an ABA, BCBA, BCaBA or RBT topic

Call the `generate_flashcards` MCP tool with a topic, a count between 3 and 20, and a difficulty. Returns term/definition pairs written to SAFMEDS brevity rules (definitions of eight words or fewer).

Quiz a learner on behaviour-analytic terminology

Call the `quiz_me` MCP tool with a topic and a question count between 3 and 10.

When not to use TAFMEDS

• Clinical decision support, diagnosis, or treatment planning for a real client — TAFMEDS is exam-preparation and fluency practice only.
• Acting on behalf of a learner under 18. TAFMEDS enforces an 18+ age gate at registration.
• Bulk-scraping the deck corpus. The card content is proprietary; the glossary and blog are the public, quotable surface.
• Reading another user’s data. Every learner-scoped tool requires that learner’s own token.

Known limitations

• There is no separate sandbox environment. Anything that does not touch learner data can be exercised directly against production.
• API credentials are per-user Firebase ID tokens that expire after one hour. There are no long-lived service accounts or machine-to-machine keys.

Endpoints and files

TAFMEDS developer resources

Self-serve onboarding

Getting started with the TAFMEDS API

There is no contact-sales step and no key-request form. Every stage below is completable on your own.

1. 1

   Try the API with no account at all

   There is no separate sandbox host: production is the sandbox for everything that does not touch learner data. The MCP endpoint answers unauthenticated `initialize` and `tools/list` calls, the two content-generation tools (`generate_flashcards`, `quiz_me`) take no token, and every public page serves Markdown under `Accept: text/markdown`.

   curl -sS -X POST https://tafmeds.com/mcp/mcp \
     -H 'Content-Type: application/json' \
     -H 'Accept: application/json, text/event-stream' \
     -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

2. 2

   Create a free account

   Registration is self-serve at /register and no payment method is required. The free tier includes timed SAFMEDS practice, the free deck corpus, and the Standard Celeration Chart.

   https://tafmeds.com/register

3. 3

   Generate your own API token

   Signed-in users mint a Firebase ID token from Settings → API Access. No approval step, no key request form. Tokens are bearer credentials scoped to that one user and expire after one hour; regenerate from the same screen.

   https://tafmeds.com/settings

4. 4

   Call learner-scoped tools

   Pass the token as the `auth_token` argument on MCP tools, or as `Authorization: Bearer <token>` on HTTP endpoints. Requests are rate limited per user; back off on HTTP 429 and honour the `Retry-After` header.

Authentication

How TAFMEDS authenticates API callers

Content for agents

Markdown from any public URL

Every public TAFMEDS page serves a Markdown representation from its own URL when you ask for it, following acceptmarkdown.com. Responses carry Content-Type: text/markdown; charset=utf-8 and Vary: Accept. Unknown paths return a real HTTP 404 with a Markdown body listing where to go next.

curl -sS -H 'Accept: text/markdown' https://tafmeds.com/glossary