Fluid Recall
API by Fluid Recall · rest
System of record for spaced recall. One service with four doors: MCP at POST /mcp (also /api/mcp), Markdown /api/v1/agent and /api/v1/dev, and JSON /api/v1. Agents may use whatever works best. None is deprecated. JSON operations sit at the /api/v1 root (/due, /decks, /reviews). Request bodies are JSON. Markdown responses use Content-Type text/plain; the body is Markdown. MCP is stateless Streamable HTTP. Send Authorization: Bearer <token>. No Mcp-Session-Id. The same MCP door speaks the ChatGPT MCP Events subset (events/list, events/subscribe, events/unsubscribe) with webhook-only delivery. Muse bootstraps a personal API token with POST /accounts or POST /bootstrap and keeps drilling. The bearer token is the tenant. This API decides what is due and when it is due next. Bootstrap, reviews, and unauthenticated reads are rate limited. HTTP 429 is retryable. ---
Endpoint: https://fluidrecall.com/api/v1
Verification: observed. Source: crawl.
Capabilities (99)
- Create an account and mint a token
- List submitted feedback
- Set a feedback card status
- Read traffic counters
- Break-glass revoke
- Add many cards and confirm in Markdown
- Correct a card and confirm in Markdown
- Move a card to another deck and confirm in Markdown
- Set or clear a card coaching note (Markdown)
- Retire a card and confirm in Markdown
- Undo the latest review and confirm in Markdown
- Restore a retired card and confirm in Markdown
- Archive a deck and confirm in Markdown
- List prompts for edit or retire
- Set or clear a deck coaching note (Markdown)
- Restore an archived deck and confirm in Markdown
- List owned mailboxes (Markdown)
- Create or claim a mailbox (Markdown)
- Read one message including the body (Markdown)
- List message headers (Markdown)
- Reply to one owned message (Markdown)
- Send from an owned mailbox (Markdown)
- Record a review and return the next prompt
- List due and the first prompt
- Bootstrap if needed then the first due prompt