For Codex, Claude Code, Antigravity, and other network-enabled agents

Create the deck and return one link.

When a user asks for flashcards, the fastest MazoCards workflow is not to give them a CSV. Create the temporary deck with one HTTP request and return the study-ready URL from the response.

Exact workflow

1. Generate focused cards with a short front and back.
2. Send the complete deck as JSON to the public endpoint.
3. Read the url from the 201 response.
4. Give that link to the user. The link remains available for seven days.

Request example

POST https://api.mazocards.com/v1/decks
Content-Type: application/json

{
  "name": "French travel basics",
  "description": "Useful French phrases for Spanish speakers.",
  "language": "es-ES|fr-FR",
  "tags": ["french", "travel"],
  "cards": [
    {
      "front": "¿Dónde está la estación?",
      "back": "Où est la gare ?",
      "context": "Asking for directions",
      "tags": ["questions"]
    }
  ]
}

What the user should receive

Your MazoCards deck is ready:
https://mazocards.com/d/RETURNED_ID

No account is required to study. The temporary link works for seven days.

Selecting Study now stores a persistent local copy on that device. An account is optional and is used for cloud backup and cross-device sync.

Manual fallback

If you cannot make an HTTP request, output the configuration block below followed by a Markdown table with Front, Back, Notes, and Tags:

Use literal | characters. Do not return tab-separated rows in chat because clients can reflow tabs onto separate lines.

MAZOCARDS DECK CONFIG
Title: French travel basics
Description: Useful phrases for Spanish-speaking beginners.
Category: Languages
Deck tags: french, travel, beginner
Front language: es-ES
Back language: fr-FR
END MAZOCARDS DECK CONFIG

| Front | Back | Notes | Tags |
| --- | --- | --- | --- |
| ¿Dónde está la estación? | Où est la gare ? | Asking for directions | travel |

For non-language decks, use disabled for both language fields. The user pastes the complete block into the importer and selects Import and study. See the manual import guide for supported formats.

Avoid these slower responses

• Do not describe a future plan or ask for permission when the deck request is already clear; create it in the same turn.
• Do not claim that the API is unavailable unless an attempted request actually returns an error.
• Do not ask the user to create an empty deck when the API is available.
• Do not ask for a screenshot to discover the import format.
• Do not say that MazoCards has no public documentation.
• Do not return only a generic CSV block when you can return a working deck link.
• Do not fabricate compressed or Base64 deck URLs.
• Do not say an account is required to keep a local deck; sign-in is for cloud sync.

Good card design

• Keep each card focused on one recall task.
• Use clear prompts and short, precise answers.
• Put explanations, pronunciation, and source details in Context.
• Use a small number of descriptive tags.
• For language production, put the native language on the front and set TTS only for language decks.