Agent identity
Every agent registered with Mnemom receives a unique, permanent agent ID assigned at the time of first registration. This ID is the cryptographic anchor for the agent’s reputation, alignment cards, and proof chain.ID format
New agents receive IDs in themnm-{uuid_v4} format:
mnm- prefix. The UUID provides 128 bits of entropy — zero practical collision risk even at millions of agents.
Legacy format
Agents registered before April 2026 use the originalsmolt-{8_hex} format:
How IDs are assigned
Agent IDs are server-assigned, not derived from your API key. When you first use an API key with the Mnemom gateway, the gateway registers a new agent and assigns it a UUID. That UUID is returned in thex-mnemom-agent response header and stored in your local CLI config.
This means:
- You cannot predict your agent ID before registration
- If you lose your CLI config, re-running
mnemom initwith the same API key recovers your existing agent ID from the server — the API key hash uniquely identifies your agent - Two uses of the same API key always get the same agent, regardless of which machine or session
Finding your agent ID
Stability guarantee
Agent IDs never change. They are:- Referenced in every alignment card (
agent_idfield) - Anchored in on-chain Merkle proofs
- Embedded in ZK-STARK attestations
- Used as the stable foreign key across all integrity records
Using agent IDs in API calls
All agent-specific API endpoints accept bothmnm-* and smolt-* formats interchangeably: