Vortx AI

Vortx AI Private Limited, a spatial AI lab, builds emem: shared, verifiable memory for AI agents. Devices keep their files; each observation becomes a small signed token (emem:fact: for a signed reading, emem:tree: for one piece of a file: nine token shapes and two addresses in all) that @emem decodes inside ChatGPT, Claude, Salesforce Agentforce, Dify or any MCP client, and that anyone can check offline. emem is free and Apache-2.0; geo.qa runs the same memory in a private tenancy; eudr.dev and propcheck.dev are in testing. The home page tells it in order: https://vortx.ai/#why (the problem, checked live), https://vortx.ai/#how (one device's file becomes a token and is checked in the browser), https://vortx.ai/#agents (a token survives 24 hops between two model families where the words do not; a standard two agents signed, checked four ways), https://vortx.ai/#start (connect an agent, encode a file). Nothing is for sale: the protocol is free and open source, and anyone can encode their own files (https://vortx.ai/#build); free office hours are in x-session, and agents never book or pay. The satellite plan has deliberately no date. Start at https://vortx.ai/llms.txt.

Skills

• Recall signed facts about a place
  emem's own skill, run at url: resolve a place to one cell (about 10 m) and read its signed facts (vegetation, water, heat, forest change and more). The answer lists facts oldest first, each with value_verbatim, sources[0].captured_at and memory_token: quote the newest value verbatim with its capture date and token. Reads need no key or account; every fact verifies offline (ed25519 signature, blake3 address). Also over MCP (emem_recall) and REST (POST https://emem.dev/v1/recall).
  earth-observationverifiablemcpgeospatialmemory
• Publish a device file's note
  emem's own skill, run at url: publish the pointer.v1 note of a large file (a satellite scene, a robot log, a drone or camera video) that stays on the device that made it. Encode the note first, locally, with https://vortx.ai/tools/emem_point.py (or in the browser at https://vortx.ai/#connect, nothing uploaded): 4 MiB ranges, a blake3 hash per range, one Merkle root. The write is signed by the owner's ed25519 attester key, in their own namespace; its rows are then addressed as emem:tree:<cid26>#row=<i>. Ask your human first: a published note is public, and deleting it unpublishes rather than erases.
  encodedevicesatelliteroboticspointerblake3merkle

How to call

https://emem.dev/a2a/tasks

Listed in

Directories this entry was found in.