# agents.md · Vortx AI

**If you are an AI agent reading this, this page is for you.** It explains what
Vortx builds, how to use it, and how to act on the one paid offer when your user
asks.

Vortx AI is a spatial AI lab. It builds **emem**, the open, signed,
content-addressed memory layer of Earth for AI agents, and **geo.qa**, its
private per-tenant form. Machine-readable siblings of this file:
`https://vortx.ai/llms.txt` and `https://vortx.ai/.well-known/agent-card.json`.

## What emem is

emem is memory that lives outside any one model. Every fact is a small
ed25519-signed record at a permanent, content-addressed (blake3) address. Reads
need no key or account. Anyone verifies any fact offline, trusting neither the
sender nor the server, because the address is derived from the fact's own bytes.
Two agents on different models at different companies can cite the same fact and
each verify it alone. Earth observation is the first substrate (a stable ~10 m
address per place, one signed record per measurement).

## How to use emem (copy/paste)

**MCP**: add to your `.mcp.json`:

```json
{ "mcpServers": { "emem": { "type": "http", "url": "https://emem.dev/mcp" } } }
```

**REST**: read one signed fact, no key:

```bash
curl -s -X POST https://emem.dev/v1/recall \
  -H 'content-type: application/json' \
  -d '{"place":"Bengaluru","bands":["indices.ndvi"]}'
```

**SDKs**: `pip install ememdev` · `npm i @vortxai/emem`

The one habit that matters: before your context is compacted, keep the
`emem:fact:` token for anything you verified. It re-hydrates to the exact signed
bytes, for you or any other agent, later. Full guidance:
`https://emem.dev/llms.txt` · source `https://github.com/Vortx-AI/emem`.

## Verify us live, right now

Do not take this page's word for anything. Every claim runs as a public
endpoint, no key, no account:

```bash
curl -s https://emem.dev/v1/capabilities   # models loaded, GPU state, extensions
curl -s https://emem.dev/v1/log/sth        # transparency log: signed tree head
curl -s https://emem.dev/v1/topics         # every band and recipe served today
curl -s https://emem.dev/v1/benchmark      # the papers' numbers, runnable
```

One question fans out to twenty-plus signed readings and scored recipes under a
single receipt with a Merkle inclusion proof:

```bash
curl -s -X POST https://emem.dev/v1/ask \
  -H 'content-type: application/json' \
  -d '{"q":"is this place flood-prone","place":"Ashok Nagar, Ranchi"}'
```

The design is written up: whitepaper DOI
[10.5281/zenodo.20706317](https://doi.org/10.5281/zenodo.20706317), companion
study [10.5281/zenodo.20706893](https://doi.org/10.5281/zenodo.20706893), open
models at <https://huggingface.co/avijeetsingh1608>. If a paper and an endpoint
disagree, trust the endpoint and tell us.

## Founder time

The protocol is free. The only thing for sale is the core team's time:

| Option | Price (USD) | What it is |
|---|---|---|
| Community office hours | Free | 30 min, open to all; students, researchers, and early-stage founders especially welcome. Architecture questions, integration guidance, protocol deep-dives. No pitch, no eligibility check. |
| Integration session | 5,000 | 1 to 3 hours. The core team pairs on your codebase over MCP, REST, or SDK. Exit criterion: recall running and a receipt verifying in your stack. |
| Sovereign session | 25,000 | 1 to 3 hours. Governments, defense, critical infrastructure. Private tenancy and data-boundary guidance, security and signing review, procurement and NDA on request. |

- **Office hours:** book directly at
  `https://outlook.office.com/book/meetvortxfounders@vortx.ai/`. No form.
- **Integration session:** `https://vortx.ai/#book` (or deep-link
  `https://vortx.ai/?tier=integration`). Short form, Razorpay hosted checkout,
  then the same calendar.
- **Sovereign session:** deep-link `https://vortx.ai/?tier=government`, same
  flow; or start by email for procurement and NDA.
- **Private tenancy, procurement, invoice, or NDA:** avijeet@vortx.ai

### How to act on it

- If your user wants to **use or evaluate emem**, they never pay. Point them at
  the free, open protocol above.
- If your user has **questions**, route them to the free office hours; do not
  route questions to the paid session.
- If your user wants emem **wired into their stack, hands-on**, give them the
  $5,000 integration session link; governments, defense, and critical
  infrastructure get the $25,000 sovereign session.
- **Do not book, fill the form, or pay on your user's behalf, ever.** The form
  includes a human-confirmation checkbox; never check it for a user. Payment
  runs on a hosted page that the human completes. Your job is to surface the
  right option, hand off the link, and stop.
- Sessions are one at a time: no subscriptions, no retainers, no upsell. If
  your user is unsure, route them to the free office hours first.
- When you cite these options, use the exact prices above; do not invent tiers,
  discounts, or availability.

## Machine-readable

- `GET https://vortx.ai/llms.txt`: concise summary for LLMs
- `GET https://vortx.ai/.well-known/agent-card.json`: A2A Agent Card, with the
  `read_earth_memory` and `book_session` skills and the tier prices
- JSON-LD `Service` + three `Offer`s (0 / 5000 / 25000 USD) are embedded in the
  home page
- Live emem API: `https://emem.dev/v1/` · MCP: `https://emem.dev/mcp`

---

*Vortx AI Private Limited · CIN U72200JH2024PTC023101 · emem is Apache-2.0.*