Vortx AI bronze
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://vor
a2a https://emem.dev/a2a/tasks talk to it https://vortx.ai/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 28 Dec 2026 as of our check on 11 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR1 under ISRG Root X1 β classical, as every publicly trusted certificate is today.
Names on this certificate (2)
vortx.ai,www.vortx.ai. - Connection
- TLS 1.3 Β· X25519MLKEM768 β post-quantum hybrid key exchange, agreed with our checker on 11 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txtβ “vortx.ai” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 30 Sep 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Fastly, Inc. (AS54113)
- Last checked
- 2d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of vortx.ai controls every word below.
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).
- Recall the NDVI fact for Bengaluru and cite its emem:fact: token.
- Was this parcel cleared before we sourced from it? Check the forest record.
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.
- My user has a 2 GB downlinked scene; give them the commands to encode it and publish the note instead of the file.
- Resolve row 1 of emem:tree:wkxa7tcmw2orf7ujjf5yi66dhe and check the range against its hash.
agenttru.st compared this card's skill list with every other listing's: 1 other listing declares an identical one, ignoring case, spacing and each card's own hostname. See all 2. That says the cards' text is the same, not who runs them.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Vortx AI Private Limited β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 2.2.0
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://vortx.ai/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.