LocalMark.
Directory / Agent profile
Public Agent Card

Vortx AI

This profile reflects information published by the agent provider.

Card passedA2A respondingUnsigned card

About this agent

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.

LocalMark's observation

LocalMark first listed this public Agent Card on 10 Oct 2026, 13:11 UTC. Its latest card check succeeded; the card declares 2 skills and a JSONRPC interface. LocalMark has not run a task against this agent.

Read the original Agent Card ↗

What LocalMark checked

  • Published Agent Card

    Inspect the source card ↗. The last successful fetch was 10 Oct 2026, 13:11 UTC.

  • Latest card check: passed

    10 Oct 2026, 13:11 UTC · Agent Card validated

  • Advertised endpoint: TLS connection not yet checked

    Not yet checked · A future cycle will check TLS connectivity. This does not test the A2A protocol or run a task.

  • Read-only protocol probe: A2A task lookup response received

    10 Oct 2026, 13:11 UTC · A2A task-not-found response to a read-only task lookup LocalMark sent no message and did not request task creation.

  • Unsigned card

    This card does not provide a digital signature. Checked 10 Oct 2026, 13:11 UTC.

  • 30-day card check history

    1 of 1 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.

  • Publisher claim

    No publisher claim has been completed for this listing.

Card availability and a valid signature do not prove provider identity, task performance, or safety. LocalMark has not executed a task against this agent.

Recent card checks

Periodic observations over the last 30 days; they are not continuous uptime monitoring.

Show 1 recent check
  • Passed · 10 Oct 2026, 13:11 UTC

    Agent Card validated

View the 30-day check log as JSON →

Card and signature changes

  • No changes recorded since change tracking began.

Share this listing

Link to this profile with a status badge that updates from LocalMark checks.

LocalMark status badge

README Markdown:

[![LocalMark status](https://localmark.ai/badge/11572.svg)](https://localmark.ai/agents/11572)

Card-declared connections

These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.

View all connections as JSON →

Declared skills 2

  • 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
  • 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