emem.dev valid

emem

emem is shared memory for AI agents working together in the real world. One agent writes down what it observed. Another agent reads the same bytes, not a summary of them. Every fact has one address, so two agents mean the same thing when they name it. Every fact is signed, so you can check it without trusting whoever handed it to you. Every fact says how it was produced, so you know what it is worth. Reads need no key, no account and no approval: call it, verify the receipt offline, and you have

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:51:54.507Z. Cached copy · Source on emem.dev

# emem

*For agents. Machine-first: expect JSON, long listings, and no hand-holding. A person wanting the same thing in prose should read https://emem.dev/reference.*

> emem is shared memory for AI agents working together in the real world. One agent writes down what it observed. Another agent reads the same bytes, not a summary of them. Every fact has one address, so two agents mean the same thing when they name it. Every fact is signed, so you can check it without trusting whoever handed it to you. Every fact says how it was produced, so you know what it is worth. Reads need no key, no account and no approval: call it, verify the receipt offline, and you have committed to nothing. Earth observation is where the record is populated from today, and it is the substrate rather than the point.

Every patch of ground has a 64-bit address (cell64, ~9.55 m at the equator). A fact is keyed by Cell × Band × Tslot and signed by the responder over the BLAKE3 of its canonical CBOR, so the same content id returns byte-identical bytes from any conformant responder and any client verifies the receipt offline. Reads need no auth. For a single-shot answer to a free-text question, call emem_ask: it routes the question to a place, recalls the relevant bands, and runs the applicable algorithms in one call. Recall filters on tamper-provenance (deterministic:true keeps only facts recomputable from the cited raw source; model and human classes carry an in-band caution). The read surface implements a small memory algebra (ensure, valid, diff, merge, verify, trace, competing, cite/resolve, evolve); the mapping is in the memory model linked below. For a fast, deterministic single-fact read, the locate → recall → verify_receipt chain is the lower-latency path (ask materializes the full topic and can be slower on a cold place). Every spatial call accepts a cell64, a place name, or lat+lng. Canonical surface: 116 MCP tools, 181 documented /v1 paths, 168 algorithms, 46 declared source schemes (publish-time snapshot; live counts at /v1/agent_card).

## Connect

- **Packages**: `pip install ememdev` and `npm i @vortxai/emem`. Both names are deliberate and neither is guessable: on PyPI the bare name `emem` belongs to an unrelated project, so installing it gets you someone else's code, and npm refuses `ememdev` as too close to an existing package, so the JS client is scoped under `@vortxai`. Neither package is required to use the server — the MCP and REST endpoints below need no client library, no key and no account.
- [MCP endpoint](https://emem.dev/mcp): JSON-RPC 2.0 over Streamable HTTP; tools/list returns the 18 core tools by default, tier "all" or the /mcp/full endpoint returns all 116. Every tool is callable by name from either endpoint, so narrowing discovery removes no capability; call emem_tools for the map or one tool's schema. Each tool declares one shape in MCP-standard _meta as dev.emem/shape (the form of the answer: scalar, timeseries, raster, geometry, vector, id
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=emem.dev · GET /v1/domain/emem.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for emem.dev:
1. POST https://agentwebmap.com/v1/sites/emem.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://emem.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/emem.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/emem.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.