emem, the verifiable memory protocol for the physical world
REMOTE · EMEM.DEV · 2 COMPONENTS · SCANNED AUG 4
Shared, verifiable memory for AI agents and robots: signed tokens that resolve and verify offline.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (memory_create). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 40357 tokens (~328/item across 123 items; 105 tools + 18 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · emem.dev
claude mcp add --transport http vortx-ai-emem https://emem.dev/mcp
[mcp_servers.vortx-ai-emem] url = "https://emem.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vortx-ai-emem": {
"type": "remote",
"url": "https://emem.dev/mcp",
"enabled": true
}
}
} openclaw mcp add vortx-ai-emem --url https://emem.dev/mcp --transport streamable-http
mcp_servers:
vortx-ai-emem:
url: "https://emem.dev/mcp" {
"mcpServers": {
"vortx-ai-emem": {
"type": "http",
"url": "https://emem.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +3
- Schema quality: unverified → poor ▲ functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 26 −3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “emem_bands” rewrote its description, which is the text the model reads security
- Tool “emem_burn_severity” rewrote its description, which is the text the model reads security
- Tool “emem_capabilities” rewrote its description, which is the text the model reads security
- Tool “emem_cell_geojson” rewrote its description, which is the text the model reads security
- Tool “emem_cell_scene_rgb” rewrote its description, which is the text the model reads security
- Tool “emem_compare_bands” rewrote its description, which is the text the model reads security
- Tool “emem_coverage_map” rewrote its description, which is the text the model reads security
- Tool “emem_coverage_matrix” rewrote its description, which is the text the model reads security
- Tool “emem_data_availability” rewrote its description, which is the text the model reads security
- Tool “emem_deforestation_alert” rewrote its description, which is the text the model reads security
- Tool “emem_edges_recall” rewrote its description, which is the text the model reads security
- Tool “emem_elevation” rewrote its description, which is the text the model reads security
- Tool “emem_embedding_centroid” rewrote its description, which is the text the model reads security
- Tool “emem_errors” rewrote its description, which is the text the model reads security
- Tool “emem_eudr_dds” rewrote its description, which is the text the model reads security
- Tool “emem_explain_algorithm” rewrote its description, which is the text the model reads security
- Tool “emem_fetch” rewrote its description, which is the text the model reads security
- Tool “emem_field_boundaries” rewrote its description, which is the text the model reads security
- Tool “emem_fleet” rewrote its description, which is the text the model reads security
- Tool “emem_heat_solve” rewrote its description, which is the text the model reads security
- Tool “emem_hunt” rewrote its description, which is the text the model reads security
- Tool “emem_intent” rewrote its description, which is the text the model reads security
- Tool “emem_jepa_predict” rewrote its description, which is the text the model reads security
- Tool “emem_jepa_predict_v2” rewrote its description, which is the text the model reads security
- Tool “emem_log_sth” rewrote its description, which is the text the model reads security
- Tool “emem_log_witnesses” rewrote its description, which is the text the model reads security
- Tool “emem_memory_contradictions” rewrote its description, which is the text the model reads security
- Tool “emem_memory_search” rewrote its description, which is the text the model reads security
- Tool “emem_neighborhood_consistency” rewrote its description, which is the text the model reads security
- Tool “emem_recall_many” rewrote its description, which is the text the model reads security
- Tool “emem_recall_polygon” rewrote its description, which is the text the model reads security
- Tool “emem_region_similarity” rewrote its description, which is the text the model reads security
- Tool “emem_rice_ch4” rewrote its description, which is the text the model reads security
- Tool “emem_sar_forest_disturbance” rewrote its description, which is the text the model reads security
- Tool “emem_sources” rewrote its description, which is the text the model reads security
- Tool “emem_state” rewrote its description, which is the text the model reads security
- Tool “emem_state_multi” rewrote its description, which is the text the model reads security
- Tool “emem_temporal_route” rewrote its description, which is the text the model reads security
- Tool “emem_topics” rewrote its description, which is the text the model reads security
- Tool “emem_trajectory” rewrote its description, which is the text the model reads security
- Tool “emem_triple_consensus” rewrote its description, which is the text the model reads security
- Tool “memory_delete” rewrote its description, which is the text the model reads security
- Tool “memory_str_replace” rewrote its description, which is the text the model reads security
- Tool “emem_terrain” rewrote its description, which is the text the model reads security
- Tool “emem_air” rewrote its description, which is the text the model reads security
- Tool “emem_verify_receipt” rewrote its description, which is the text the model reads security
- Tool “emem_algorithms” rewrote its description, which is the text the model reads security
- Tool “emem_ask” rewrote its description, which is the text the model reads security
- Tool “emem_backfill” rewrote its description, which is the text the model reads security
- Tool “emem_band_raster” rewrote its description, which is the text the model reads security
- Schema quality: good → poor functional
- Server version: 1.2.1 → 1.3.0 functional
- New tool “emem_reason” functional
- New tool “emem_substrates” functional
- New tool “emem_trace_verify” functional
- “emem_compare_bands” reworded the description of “tslot_a” cosmetic
- “emem_derive” reworded the description of “code_cid” cosmetic
- “emem_derive” reworded the description of “provenance_class” cosmetic
- “emem_edges_recall” reworded the description of “obj” cosmetic
- “emem_elevation” reworded the description of “cell” cosmetic
- “emem_field_boundaries” reworded the description of “zoom” cosmetic
- “emem_find_similar” reworded the description of “as_of_tslot” cosmetic
- “emem_find_similar” reworded the description of “band” cosmetic
- “emem_find_similar” reworded the description of “mode” cosmetic
- “emem_forest” reworded the description of “band” cosmetic
- “emem_forest” reworded the description of “bands” cosmetic
- “emem_hunt” reworded the description of “event” cosmetic
- “emem_locate” reworded the description of “q” cosmetic
- “emem_lst” reworded the description of “band” cosmetic
- “emem_lst” reworded the description of “bands” cosmetic
- “emem_memory_contradictions” reworded the description of “window_unix_s” cosmetic
- “emem_memory_search” reworded the description of “q” cosmetic
- “emem_memory_token” reworded the description of “cell” cosmetic
- “emem_ndvi” reworded the description of “band” cosmetic
- “emem_ndvi” reworded the description of “bands” cosmetic
- “emem_query_region” reworded the description of “as_of_tslot” cosmetic
- “emem_raster_resolve” reworded the description of “spot_check” cosmetic
- “emem_recall” reworded the description of “as_of_signed_at” cosmetic
- “emem_recall” reworded the description of “as_of_tslot” cosmetic
- “emem_recall” reworded the description of “band” cosmetic
- “emem_recall” reworded the description of “deterministic” cosmetic
- “emem_recall” reworded the description of “provenance” cosmetic
- “emem_recall_many” reworded the description of “bands” cosmetic
- “emem_recall_polygon” reworded the description of “as_of_tslot” cosmetic
- “emem_recall_polygon” reworded the description of “include” cosmetic
- “emem_recall_polygon” reworded the description of “projection” cosmetic
- “emem_rice_ch4” reworded the description of “cultivation_period_days” cosmetic
- “emem_rice_ch4” reworded the description of “efc_kg_ch4_ha_day” cosmetic
- “emem_soil” reworded the description of “band” cosmetic
- “emem_soil” reworded the description of “bands” cosmetic
- “emem_state” reworded the description of “as_of_tslot” cosmetic
- “emem_state_multi” reworded the description of “as_of_tslot” cosmetic
- “emem_temporal_route” reworded the description of “intent” cosmetic
- “emem_trajectory” reworded the description of “as_of_tslot” cosmetic
- “emem_water” reworded the description of “band” cosmetic
- “emem_water” reworded the description of “bands” cosmetic
- “emem_weather” reworded the description of “band” cosmetic
- “emem_weather” reworded the description of “bands” cosmetic
- “emem_air” reworded the description of “band” cosmetic
- “emem_air” reworded the description of “bands” cosmetic
- “emem_ask” reworded the description of “cell” cosmetic
- “emem_at” reworded the description of “band” cosmetic
- “emem_at” reworded the description of “bands” cosmetic
- “emem_backfill” reworded the description of “band” cosmetic
- Tool “emem_embedding_centroid” changed its title: Embedding centroid — mean-pooled GeoTessera vector for a region → Embedding centroid, mean-pooled GeoTessera vector for a region cosmetic
- Tool “emem_embedding_diversity” changed its title: Embedding diversity — landscape heterogeneity over a region → Embedding diversity, landscape heterogeneity over a region cosmetic
- Tool “emem_eudr_dds” changed its title: EUDR Due Diligence Statement — polygon-in, signed Annex II envelope out → EUDR Due Diligence Statement, polygon-in, signed Annex II envelope out cosmetic
- Tool “emem_hunt” changed its title: Hunter mode — find event hotspots over a region → Hunter mode, find event hotspots over a region cosmetic
- Tool “emem_memory_search” changed its title: emem_memory_search — semantic search over /memories/* files → emem_memory_search, semantic search over /memories/* files cosmetic
- Tool “emem_region_similarity” changed its title: Region similarity — cosine of two regions' mean GeoTessera embeddings → Region similarity, cosine of two regions' mean GeoTessera embeddings cosmetic
- Tool “emem_terrain” changed its title: Terrain triad — slope + ruggedness + topographic position from DEM → Terrain triad, slope + ruggedness + topographic position from DEM cosmetic
- Tool “memory_create” changed its title: memory_create — write a memory file (overwrite if exists) → memory_create, write a memory file (overwrite if exists) cosmetic
- Tool “memory_delete” changed its title: memory_delete — remove a memory file or directory → memory_delete, remove a memory file or directory cosmetic
- Tool “memory_insert” changed its title: memory_insert — insert at a given line → memory_insert, insert at a given line cosmetic
- Tool “memory_list_by_kind” changed its title: memory_list_by_kind — typed enumeration of memory files → memory_list_by_kind, typed enumeration of memory files cosmetic
- Tool “memory_rename” changed its title: memory_rename — move a memory file → memory_rename, move a memory file cosmetic
- Tool “memory_view” changed its title: memory_view — read file or directory listing → memory_view, read file or directory listing cosmetic
- Tool “memory_str_replace” changed its title: memory_str_replace — exact-string replacement in a memory file → memory_str_replace, exact-string replacement in a memory file cosmetic
- 27 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Aug 2026 · Probed https://emem.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=emem.dev | CN=YE1,O=Let's Encrypt,C=US | 25 Jun 2026 | 23 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 585b40324d02015c7ffa469b0dc392dd4a8 |
| SANs: emem.dev, www.emem.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of emem.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| emem.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' https://www.googletagmanager.com https://esm.sh https://cdn.redocly.com 'sha256-1LQb9Vhps9539K8WtLY4YJCvLqfXXHHrFKFU9lO7yDo=' 'sha256-3vokV7ulOzXmEDPT8jHerCF3DotZc5zDsH+ktR8/bQg=' 'sha256-5drXHcFDsHyX/M9ryszbgZHB7YSCe55jIHn/02mKXPw=' 'sha256-8vnQX7+vHcAt3ELB02aOu4MJIM+256eIdW2+xkLr5ac=' 'sha256-BC3kmFRQjI7i3nY+wYMTbt65j6ljlx+ZN433t/kignI=' 'sha256-BCnJeyXiJpn+/3NNsV51yA064CoZ8FJsey8VGQBHnM8=' 'sha256-BuChz52GVMz8nc76A+SoFZTTc+l8J0PvArPG3PF9GAE=' 'sha256-BwiUvoXcoNy0+qgJzFyEd7Q/AC9W8wpF6jwhJqdAXC4=' 'sha256-CHjGNtQ7K1LwQzVfsQaI5HpMPnT/QUFevTLL+ir1EE0=' 'sha256-D18y043mO+yptyU9fUFvoFL8ZhV2+JbGm/GzXbHoER8=' 'sha256-ESM3y/M07WghKtExySfU1rCnornbOI7uIwzL3Ngu+ok=' 'sha256-GKaIUE1muvRIoxngaNj1LRkSVR2DROt1XVsNzhyI2js=' 'sha256-JncTJLIIYKBmqB4e18NO64h1JN22U2SsMTZXAeD5db8=' 'sha256-MM8UG+X+sxn1SSO3vbj0Q/JHl9Ekn4SS1eg4MOnAIeU=' 'sha256-Nt0FXER1PgT47bnh3eP4amurWD7ly8tLVRAmcCvhk+w=' 'sha256-OgLVXQgwqGXNUbOLG2XzC/cqA1NCgR635CscyVTF6Kg=' 'sha256-RtmdiUQ8ytLlWLjL0uoPLD2w1CqKFVw9iF5YrcdnCI |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://emem.dev/mcp | Verified | 200 | |
| http (plaintext) | http://emem.dev/mcp | HTTPS enforced | 308 | https://emem.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
memory_insert memory_insert, insert at a given line ~413
Insert `new_str` after the given 1-indexed line in the named memory file. `insert_line: 0` inserts at the top. Writes a new `file_cid` and signs the receipt. Mirrors the `insert` verb in Anthropic's context-management-2025-06-27 memory tool spec. WRITES ARE SIGNED, NOT ANONYMOUS: supply `attester: {pubkey_b32, sig_b32}`, an ed25519 signature over blake3("emem.memory_write|<verb>|<path>|<body_hash>"); an unattested write is refused with the exact digest to sign. Under `/memories/by_attester/<pubkey8>/...` only the matching key may write. Elsewhere the first attester to create a path owns it and only that key may change it. Stored content is world-readable by design: this is a shared commons, not private storage. When to use: Call when the LLM wants to append a new line to a memory file without rewriting it. For top-of-file inserts, pass `insert_line: 0`; for end-of-file, pass the current line count (the responder rejects out-of-range with a typed error). Example arguments: {"path":"/memories/by_attester/<your-pubkey8>/notes.md","insert_line":0,"new_str":"draft 2026-05-28"}
| Name | Type | Req | Description |
|---|---|---|---|
| attester | object | — | Optional ed25519 caller binding. See memory_create for the preimage shape (verb=insert). |
| insert_line | integer | yes | 1-indexed line number AFTER which to insert. 0 inserts at the top of the file. |
| kind | string | — | Optional memory typing override. If omitted the existing kind is preserved. |
| new_str | string | yes | Text to insert. A trailing newline is preserved if present; one is added otherwise. |
| path | string | yes | `/memories/<file>` path the insertion targets. |
No output schema declared.
No examples provided.
memory_list_by_kind memory_list_by_kind, typed enumeration of memory files ~270
List memory files by their typed `kind` (episodic | semantic | procedural | resource). Optional path prefix narrows the scan; results are sorted by signed_at descending. The kind taxonomy follows the CoALA / LangMem / MIRIX agent-memory ontology: `episodic` = observations of events, `semantic` = durable learned facts, `procedural` = playbooks, `resource` = generic durable scratchpad (default for back-compat). Reads are public: no key, no account, and every stored memory on this responder is world-readable, including files other agents wrote. Do not put anything private here. When to use: Call when an agent wants only one slice of its memory (e.g. surface every semantic fact it has learned about a topic) without scanning the full directory tree. Pair with memory_view for read-back of a specific entry. Example arguments: {"kind":"semantic","prefix":"/memories/","limit":50}
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Memory type to enumerate. |
| limit | integer | — | Maximum entries to return (default 256, cap 2048). Results are sorted signed_at desc. |
| prefix | string | — | Optional path prefix filter, e.g. `/memories/by_attester/abcd1234/`. |
No output schema declared.
No examples provided.
memory_rename memory_rename, move a memory file ~422
Move (rename) a memory file from `old_path` to `new_path`. Both paths must stay under `/memories/`; `new_path` must not already exist. The file_cid is preserved (no re-sign) so the prior receipt still binds the bytes. Mirrors the `rename` verb in Anthropic's context-management-2025-06-27 memory tool spec. WRITES ARE SIGNED, NOT ANONYMOUS: supply `attester: {pubkey_b32, sig_b32}`, an ed25519 signature over blake3("emem.memory_write|<verb>|<path>|<body_hash>"); an unattested write is refused with the exact digest to sign. Under `/memories/by_attester/<pubkey8>/...` only the matching key may write. Elsewhere the first attester to create a path owns it and only that key may change it. Stored content is world-readable by design: this is a shared commons, not private storage. When to use: Call when the LLM wants to rename or move a memory file. Failure modes: source missing, destination already exists, path escapes `/memories/`. Example arguments: {"old_path":"/memories/by_attester/<your-pubkey8>/notes.md","new_path":"/memories/by_attester/<your-pubkey8>/archive/notes-2026-05.md"}
| Name | Type | Req | Description |
|---|---|---|---|
| attester | object | — | Optional ed25519 caller binding (verb=rename). Required when either path is under `/memories/by_attester/<pubkey8>/...`. One signature binds both ends of the move: sig signs blake3("emem.memory_write… |
| new_path | string | yes | Destination `/memories/<file>` path. Fails when the destination exists. |
| old_path | string | yes | Existing `/memories/<file>` path. |
No output schema declared.
No examples provided.
memory_str_replace memory_str_replace, exact-string replacement in a memory file ~406
Replace `old_str` with `new_str` in the named memory file. Fails (no partial write) when `old_str` is absent or matches more than once. Writes a new content-addressed `file_cid` and signs the receipt. Mirrors the `str_replace` verb in Anthropic's context-management-2025-06-27 memory tool spec. WRITES ARE SIGNED, NOT ANONYMOUS: supply `attester: {pubkey_b32, sig_b32}`, an ed25519 signature over blake3("emem.memory_write|<verb>|<path>|<body_hash>"); an unattested write is refused with the exact digest to sign. Under `/memories/by_attester/<pubkey8>/...` only the matching key may write. Elsewhere the first attester to create a path owns it and only that key may change it. Stored content is world-readable by design: this is a shared commons, not private storage. When to use: Call when the LLM issues a `str_replace` against its memory file, typical for small targeted edits. The strict single-match contract is the contract Claude expects: an LLM that sees a single-match diff knows the change applied where it intended. Example arguments: {"path":"/memories/by_attester/<your-pubkey8>/notes.md","old_str":"read the brief","new_str":"finished the brief"}
| Name | Type | Req | Description |
|---|---|---|---|
| attester | object | — | Optional ed25519 caller binding. See memory_create for the preimage shape (verb=str_replace). |
| kind | string | — | Optional memory typing override. If omitted the existing kind is preserved. |
| new_str | string | yes | Replacement substring. |
| old_str | string | yes | Exact substring to replace. The whole call fails (no partial write) when the old_str is absent or appears more than once. |
| path | string | yes | `/memories/<file>` path the replacement targets. |
No output schema declared.
No examples provided.
memory_view memory_view, read file or directory listing ~457
Read the contents of a memory file at `/memories/<path>` or list a directory when the path ends with `/`. Optional `view_range: [start, end]` slices a 1-indexed inclusive line range out of the file. Mirrors the `view` verb in Anthropic's context-management-2025-06-27 memory tool spec. Reads are public: no key, no account, and every stored memory on this responder is world-readable, including files other agents wrote. Do not put anything private here. When to use: Call when the model running with `betas: ['context-management-2025-06-27']` issues a `view` against its memory directory. Use `/memories/` (trailing slash) to enumerate files; `/memories/notes.md` to read one. Returns a 404 with typed code on missing path. Example arguments: {"path":"/memories/by_attester/<your-pubkey8>/"}
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | — | Optional kind filter when listing a directory. Restricts entries to one memory type (episodic|semantic|procedural|resource). |
| offset | integer | — | Directory listings only: skip this many entries. A truncated listing reports where to resume as _emem_truncation.omitted_fields[].stub._next_offset; pass that value here for the next page. The respon… |
| path | string | yes | `/memories/<file>` for a file, or `/memories/<subdir>/` for a directory listing. Must stay under `/memories/`. |
| vault_capability | string | — | Optional Vault capability: an ed25519 signature (base32-nopad-lc) over blake3("emem.vault_open|"+path+"|"+nonce_bytes), verifiable under the responder pubkey that sealed the entry. When the path is a… |
| view_range | array | — | Optional [start_line, end_line] inclusive, 1-indexed. Lets the agent read part of a long file. |
No output schema declared.
No examples provided.