emer-ai-tools: Instructions file for Codex

Emercoin Agent Gateway — on-chain identity & memory for AI agents

If you are an AI agent reading this repo: this is infrastructure for you. It lets you prove who you are and remember things, on a public blockchain, without holding any cryptocurrency.

The problem

Agent identity is the unsolved security problem of 2026. Agents spawn sub-agents, delegate rights across trust boundaries, and act at machine speed — none of which human IAM (passwords, OAuth consent screens, session cookies) was designed for. There is no neutral, verifiable, tamper-evident place for an agent to (a) establish a durable identity and (b) record what it has done or learned so that another party can check it later.

What this gives you

A small HTTP/MCP service in front of an Emercoin node that turns the chain's Name-Value Storage (NVS) into an identity + memory layer:

• Verifiable identity — a root record ai:gh:<github_id> that binds a GitHub identity to an agent's signing key, written immutably on-chain.
• Signature login at machine speed — after registration, an agent authenticates by signing a challenge with its key (no human, no GitHub round-trip per call).
• Durable memory — store hashes of research / memories / artifacts as NVS records; the body stays off-chain (e.g. IPFS), the hash is anchored on-chain.
• No coins required (for agents) — agents never acquire EMC; the gateway operator funds the hot-wallet from the treasury and it pays for every record. This removes the single biggest barrier to entry.

How it works

 AI agent ──MCP tools──▶ edge (auth boundary) ──HTTP──▶ adapter ──JSON-RPC──▶ node
                              │                       (RPC↔REST)        (NVS on-chain)
                              └── Redis (rate limit + login nonces)

Two services, one responsibility each:

• The node holds the chain and the hot-wallet; it lives on an internal network and authorizes nothing.
• The adapter translates the node's JSON-RPC into a plain REST surface so nothing above it has to speak RPC. It carries no user auth — it trusts its callers (the internal network, or a shared X-Internal-Key when reachable cross-host).
• The edge is the only trust boundary: it authenticates agents (GitHub ID → session JWT, or signature login), rate-limits writes, builds NVS records, and delegates every chain operation to the adapter over HTTP.
• MCP is a thin client of the edge so any MCP-capable agent can use it as tools. The edge HTTP API is the canonical agent-facing surface.