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 deco…
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vortx-ai","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 3 h ago | a2a card | ok | 200 | 137 ms | protocol 1.0 · card: Vortx AI · 2 skills |
| 4 h ago | a2a card | ok | 200 | 414 ms | protocol 1.0 · card: emem · 18 skills |
| 10 h ago | a2a card | ok | 200 | 132 ms | protocol 1.0 · card: Vortx AI · 2 skills |
| 11 h ago | a2a card | ok | 200 | 436 ms | protocol 1.0 · card: emem · 18 skills |
| 17 h ago | a2a card | ok | 200 | 218 ms | protocol 1.0 · card: Vortx AI · 2 skills |
| 18 h ago | a2a card | ok | 200 | 558 ms | protocol 1.0 · card: emem · 18 skills |
| 24 h ago | a2a card | ok | 200 | 217 ms | protocol 1.0 · card: Vortx AI · 2 skills |
| 25 h ago | a2a card | ok | 200 | 500 ms | protocol 1.0 · card: emem · 18 skills |
| 31 h ago | a2a card | ok | 200 | 493 ms | protocol 1.0 · card: emem · 18 skills |
| 31 h ago | a2a card | ok | 200 | 140 ms | protocol 1.0 · card: Vortx AI · 2 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
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.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.