memory.wiki API Integration Guide

This document outlines the technical specifications for interacting with the memory.wiki API, focusing on authentication protocols and document management endpoints. It provides a framework for programmatic access via CLI, MCP, or direct HTTP requests.

Key claims

  • [EXTRACTED] The memory.wiki API enforces a rate limit of 10 requests per minute per IP address [doc-1].
  • [EXTRACTED] Authentication is progressive, ranging from unauthenticated access for basic operations to JWT-based identity for CLI and MCP tools [doc-1].
  • [EXTRACTED] When creating a document, the API returns an editToken which can be used to manage updates or deletions for that specific resource [doc-1].
  • [INFERRED] The platform is designed to support multi-modal input sources, as evidenced by the source parameter which explicitly categorizes origins like "vscode," "github," and "mcp" [doc-1].
  • [AMBIGUOUS] While the API supports x-user-id and x-user-email headers for ownership verification, the documentation does not specify the exact mechanism for how allowed_emails are configured or managed [doc-1].

Cross-references

  • Authentication Methods: The API documentation distinguishes between JWT-based authentication (used by CLI/MCP) and token-based authentication (using the editToken returned upon creation) [doc-1]. These represent two distinct security tiers: one for persistent user identity and one for granular document-level control.

Open questions / gaps

  • What are the specific error codes returned when the 10 request/min rate limit is exceeded?
  • How are folderId values generated or retrieved?
  • Is there a programmatic way to list documents, or is access strictly limited to fetching by known ID?

Provenance

  • [doc-1]: Provides the technical specifications, endpoint definitions, and authentication requirements for the memory.wiki platform.