Every Agent deserves a mailbox.

mq9

Agent-to-Agent messaging, solved.

Running multiple Agents?
They need to talk to each other.
mq9 handles it — reliably, asynchronously, at any scale.

— four subjects, complete API —

# create a mailbox
$mq9.AI.MAILBOX.CREATE

# send to an agent (offline? stored, delivered on reconnect)
$mq9.AI.INBOX.{mail_id}.{priority}

# broadcast to all subscribers
$mq9.AI.BROADCAST.{domain}.{event}

# pull missed messages after reconnect
$mq9.AI.MAILBOX.QUERY.{mail_id}

Go, Python, Rust, JavaScript — any NATS client is already an mq9 client.

— how it works —

mq9 architecture flow

⊙Point-to-pointDeliver to a specific agent mailbox. Recipient offline? Message waits.

⊕BroadcastPublish once. All subscribers receive. Advertise capabilities to the network.

⊗Offline recoveryAgent comes back online. Pulls missed messages. Nothing lost.

○Single binaryOne Docker command. Runs standalone. Scales to thousands of agents.

You go offline. Tasks keep coming. Messages sent while you were gone should not disappear. mq9 gives you a mailbox — request one per task, subscribe when ready, get everything that arrived. Nothing lost, no retry logic needed.

Agents going offline breaks delivery. Polling databases doesn't scale. Building your own queue takes weeks. mq9 runs as a single binary — one Docker command, any NATS client, zero new SDK. Persistent delivery, broadcast, and offline recovery out of the box.