Question 1

What is emem?

Accepted Answer

emem is a shared, verifiable memory for AI agents. Every place on Earth gets a stable address called a cell64 (about 10 m on a side). Facts at that address (elevation, weather, land cover, foundation embeddings) are recall-able as Cell × Band × Tslot → Fact, signed with ed25519, content-addressed with blake3. There are no API keys for read endpoints.

Question 2

How do I connect Claude, Cursor, Cline, Gemini, or ChatGPT?

Accepted Answer

Point any MCP client at https://emem.dev/mcp. tools/list advertises the 18 core tools, which keeps the descriptors out of your context; call emem_tools to search the rest or fetch one tool's schema, and note that every tool stays callable by name whether or not it was advertised. Point at https://emem.dev/mcp/full instead to have all 115 registered up front. Claude Code, Claude Desktop, Cursor, Cline, Gemini CLI, and ChatGPT Custom GPTs all support Streamable HTTP MCP. For ChatGPT Actions, import https://emem.dev/openapi.action.json with auth: none.

Question 3

Does it cost anything?

Accepted Answer

L0 and L1 read endpoints are free and anonymous. No accounts, no API keys, no payment. Apache-2.0 source. Operators self-hosting their own responder pay only for their own compute.

Question 4

Can I verify the answers offline?

Accepted Answer

Yes. Every read returns a receipt with the responder's ed25519 public key, the signed payload, and the content-addressed CID for each fact. Recompute blake3 over the canonical CBOR fact, verify ed25519 against the signer pubkey, and the answer is reproducible. POST /v1/verify_receipt does this for you, or do it offline in any ed25519 + blake3 implementation.

Question 5

Where does the data come from?

Accepted Answer

Sentinel-2 L2A and Sentinel-1 GRD via the Element84 STAC, MODIS Terra/Aqua via NASA LP DAAC, Copernicus DEM, GMRT topo and bathy, JRC Global Surface Water, Hansen Global Forest Change, ESA WorldCover, SoilGrids 2.0, MET Norway nowcast weather, ECMWF ERA5 and CAMS via Open-Meteo, NASA POWER, Overture Maps. Foundation embedding: Tessera v1 (Cambridge). Earlier versions also ran Clay, Prithvi and Galileo; facts they signed still verify.

Question 6

How does emem handle GDPR, CCPA, and DPDP? Does the site track visitors?

Accepted Answer

The canonical channel carries no PII. The hosted responder logs only a blake3-hashed truncated IP (non-reversible), the request path, and GET query strings, retained for 30 days then vacuumed by systemd-journald. THE SITE RUNS NO THIRD-PARTY ANALYTICS: Google Analytics was removed, along with the consent banner and the emem_consent cookie it set, because a page whose argument is that you do not have to trust the responder should not ask you to trust a second party to count you. No cookies are set. Nothing is loaded from a third-party origin for measurement.

Give your agent a memory other agents can check.

Encode once. Decode anywhere.

One token per thing

Who writes to emem

Encoded: what agents already carry

Webb’s Cosmic Cliffs, strip by strip

Robot arms making coffee, 12 keyframes

The Amazon frontier, 2017 to 2025

GPT-2, every tensor named

The whole Earth’s terrain, 349,525 tiles

Keylong hillside, Lahaul, as splats

London street cameras, clip by clip

Ozone, 41 years of a climate model

A CT slice, in Hounsfield units

express v5.2.1, 45 sections

A holiday photo, placed by its EXIF

Lusail rising, one signed number

A cell volume, 236 slices deep

Autzen, 10.6 million lidar points

Attention Is All You Need, in 3 parts

Mars, two nights in December 2024

A scanned invoice, read and added up

Bengaluru, 144 signed squares

A machine’s own trace, chained

How it works

Decode it anywhere

Build with it