API Reference

The FishMem REST API is mem0-compatible. If you already use a mem0 client, see Migrate from mem0 — you can usually point it at FishMem and keep your existing code.

Base URL

https://fishmem.com

Authentication

Every request requires a Bearer token in the Authorization header. Keys look like fm_... — keep them server-side.

Authorization: Bearer fm_...

A missing or invalid key returns 401:

{ "code": 401, "message": "Invalid API key", "error": "INVALID_API_KEY" }

The `<memory>` object

Reads and searches return memory objects with this shape:

{
  "id": "mem_…",
  "memory": "Prefers dark mode",
  "memory_type": "fact",
  "importance": 0.7,
  "user_id": "alex",
  "agent_id": null,
  "run_id": null,
  "metadata": null,
  "created_at": "2026-01-01T00:00:00.000Z",
  "updated_at": "2026-01-01T00:00:00.000Z",
  "event_date": null,
  "valid_from": null,
  "valid_to": null
}

Search results include an additional score field.

Errors

Any failure returns JSON with the same shape:

{ "code": 404, "message": "Memory not found", "error": "NOT_FOUND" }

Field	Description
`code`	HTTP status code
`message`	Human-readable text
`error`	Machine-readable error code

Credits

Operation	Credits
Add (inferred, `infer: true`)	2
Add (raw, `infer: false`)	1
Search	1
List, Get, History	Free
Update, Delete, Delete all	Free

Endpoints

Endpoint	Method & path	Description
Add memories	`POST /v1/memories`	Extract and store memories from messages
List memories	`GET /v1/memories`	List memories in a scope
Search memories	`POST /v1/memories/search`	Semantic search within a scope
Get a memory	`GET /v1/memories/{id}`	Fetch a single memory
Update a memory	`PUT /v1/memories/{id}`	Edit a memory's text or metadata
Delete a memory	`DELETE /v1/memories/{id}`	Delete a single memory
Delete memories by scope	`DELETE /v1/memories`	Delete all memories in a scope
Memory history	`GET /v1/memories/{id}/history`	Audit trail for a memory