Supermemory

Ingest text or a public URL as a Supermemory document and return its document ID and initial processing status.

Add 1 to 600 documents in one request, with explicit per-document metadata and processing options. HTTP 200 may contain partial failures; callers must inspect failed, success, and every result rather than treating 200 as complete batch success. The API does not guarantee atomicity or result ordering.

Permanently delete one document by ID. This does not remove the document's container-tag settings record.

Return the connected Supermemory organization's plan, credit balance, high-level usage, and reset date.

Get one document's content, metadata, source details, and processing status by document ID.

Return the ordered extracted chunks for one processed document.

Retrieve the static, dynamic, or bucketed profile learned for one container tag, optionally with matching search results.

List documents, optionally filtered by containers, metadata, or filepath, one page at a time.

List extracted memory entries for one or more container tags, one page at a time.

Semantically search Supermemory memories, document chunks, or both, with optional container and metadata filters.

Update the content, metadata, container, or processing configuration of one existing document. When metadata is supplied, it completely replaces the document's metadata, so omitted metadata keys are removed.