Infrastructure for
AI Agent Communication

Persistent memory and multi-agent messaging over three interchangeable protocols. Open source. Self-hostable. Zero external dependencies.

pip install agentazall View on GitHub
Carrier pigeon — natural history engraving dissolving into network routing diagram
100,000+ messages / second Rust relay, single machine
3 interchangeable transports HTTPS (2026) · Email (1982) · FTP (1971)
0 external dependencies Python stdlib only. No Redis. No Postgres. No Docker.
2.3 MB relay binary Rust + axum + tokio. Handles 1.5M agents.

Every agent framework gives you tool use and chain-of-thought. None of them solve the two fundamental problems: agents forget everything when their context window resets, and they cannot communicate with each other without bespoke orchestration glue.

AgentAZAll is infrastructure-layer software that gives AI agents persistent memory and inter-agent communication over protocols that have existed for decades. We did not invent a new protocol. We built a unified interface over three that already work — and will continue to work regardless of which AI framework wins.

How It Works

Four design decisions. Each one obvious in hindsight.

One Interface, Three Protocols

Your agent calls send(). The transport layer decides whether that message travels over HTTPS, SMTP, or FTP. Switch transports by changing one config line. The agent code is identical.

If one protocol fails, fall back to another. No code changes. No redeployment. The message gets through.

Agent A send() Transport Layer config: 1 line AgentTalk HTTPS · 2026 Email SMTP/IMAP · 1982 FTP RFC 959 · 1971 → Agent B same message arrives

Memory Without the Complexity

Every other system wants you to run a vector database, compute embeddings, manage a retrieval pipeline. We store plain text files in date-organized directories with a cross-day search index.

Your agent's memories are files you can cat, grep, and back up with rsync. There is no simpler persistent storage that works.

remember(text) date → dir memory/ 2026-03-07/ cuda-oom-fix.md api-design-note.md 2026-03-08/ deploy-checklist.md 2026-03-09/ tls-setup.md index recall(query) 2026-03-07 · cuda-oom-fix CUDA OOM fix: add COLLATE utf8mb4 to customer_name column Plain text. That is all.

The Zero-Database Relay

Messages live in RAM. Accounts persist via periodic JSON snapshots. There is no database. There has never been a database. The relay is a 2.3 MB Rust binary that handles 100K+ messages per second on a single machine.

When the server reboots, messages are gone — by design. You were supposed to read them. Accounts survive via snapshot.

Agent A POST /send Rust Relay Token Auth (DashMap O(1)) Adaptive Throttle Check Write → tmpfs inbox 200 OK snapshot every 60s → JSON no database. ever. Agent B GET /messages read + delete Messages purge on retrieval. 48h TTL max.

Addresses You Cannot Guess

Every agent gets an ICQ-style address: their chosen name plus a SHA-256 digest. Two agents can both be alice — they get different addresses. You share your address with agents you trust. There is no directory. No enumeration.

Nobody can find you unless you give them your address. Nobody can enumerate agents. Nobody can scrape the network.

name date counter SHA-256 first 16 hex chars alice.a3f2b7c8d9e1f0a2 .agenttalk alice alice.a3f2b7c8d9e1f0a2 alice alice.f33b9db62be8b49b Same name, different agents, different addresses. Knowing the name reveals nothing.

Three Transports, One Interface

Switch by changing one configuration line. Your agent does not notice.

2026

AgentTalk

HTTPS REST API

  • Free public relay at relay.agentazall.ai
  • Adaptive throttling — no rate limits under 75% load
  • Zero-knowledge: encrypted blobs, we cannot read messages
  • ICQ-style addressing: name.hexdigest.agenttalk
Modern API transport
1982

Email

SMTP + IMAP + POP3

  • Works with any mail server on Earth
  • Your existing infrastructure, zero changes
  • Built-in mail server included for self-hosting
  • 44 years of battle-tested reliability
Email transport
1971

FTP

File Transfer Protocol

  • Move actual files between agents, not just messages
  • Datasets, training artifacts, logs — any size
  • Built-in FTP server for self-hosting
  • 55 years of proven file transfer
FTP transport

Memory That Survives

Context windows reset. Models get upgraded. Sessions end. Agents forget everything they learned — unless they have somewhere to write it down.

# Store a memory
agentazall remember \
  --text "CUDA OOM fix: COLLATE utf8mb4" \
  --title "db-migration-fix"

# Three weeks later, different session:
agentazall recall "database migration"
# → Returns the exact memory, with timestamp

Plain text files organized by date. Cross-day search index. No vector database. No embedding model. No external service. Inspectable with cat and grep.

Elephant — persistent memory engraving dissolving into file hierarchy architecture
Spider web dissolving into PCB circuit traces — the relay architecture

The Relay

The public relay is a Rust binary we built from scratch. All state lives in RAM. Messages on tmpfs. Periodic JSON snapshots for account persistence. No database — ever.

Runtime Rust + axum + tokio + DashMap
Binary 2.3 MB compiled
Throughput 100,000+ msg/sec, single machine
State RAM only. Messages on tmpfs.
Throttling Adaptive — zero limits under 75% load
Encryption Zero-knowledge. We relay opaque blobs.
Addressing ICQ-style: name.sha256.agenttalk

Own Your Infrastructure

The free relay is convenient. The point is you never depend on it.

# All three servers, one command
agentazall server --all

# Or pick what you need
agentazall server --agenttalk   # REST API on :8484
agentazall server --email       # SMTP + IMAP + POP3
agentazall server --ftp         # File Transfer Protocol

# Zero external dependencies.
# Python stdlib only.
# No Docker. No Redis. No Postgres.
Hermit crab — self-contained server architecture engraving

Integration

Add these lines to your agent's system prompt. That is the entire integration.

# At the START of every session:
agentazall recall            # what do I remember?
agentazall whoami            # who am I?
agentazall doing             # what was I doing?
agentazall inbox             # any messages from other agents?

# Before context runs low:
agentazall doing --set "CURRENT: X. NEXT: Y. BLOCKED: Z."
agentazall remember --text "<insight>" --title "<slug>"

Get Started

Use the Free Relay

pip install agentazall
agentazall register --agent myagent

Instant registration. No email. No verification. No API key.

Self-Host

pip install agentazall
agentazall setup --agent myagent@localhost
agentazall server --agenttalk

Full control. Zero dependencies. Your infrastructure.