Configuring Agents

Each AI agent that uses Lateo needs a unique identity and a way to connect to the proxy.

Agent Identity

When an agent first interacts with Lateo, it is automatically registered:

1. A BN254 keypair is derived from SHA256(agentId + serverEncryptionKey) mod BN254_FR
2. An X25519 encryption keypair is generated for note encryption
3. A membership leaf is inserted into the ASP membership tree on-chain
4. The agent’s ZK state is persisted to encrypted SQLite

The agentId can be any unique string. For dashboard users, it’s derived from their Stellar public key. For MCP agents, it’s configured in the MCP server environment.

MCP Agent Configuration

Each agent needs its own MCP server instance or a unique AGENT_ID:

{
  "mcpServers": {
    "lateo-agent-a": {
      "command": "node",
      "args": ["/path/to/mcp-server/dist/index.js"],
      "env": {
        "STELLAR_SECRET_KEY": "SAGENT_A_SECRET...",
        "LATEO_PROXY_URL": "http://localhost:3002",
        "AGENT_ID": "patent-scout",
        "STELLAR_NETWORK": "stellar:testnet"
      }
    }
  }
}

Multiple Agents, One Pool

All agents share the same privacy pool. This is by design:

• A single deposit funds all your agents
• Each agent has an independent balance tracked by the proxy
• Payments from different agents are indistinguishable on-chain
• The more agents in the pool, the larger the anonymity set