Agent to agent,
for people.

Agent-to-agent communication means one AI agent sends a message, a question or an answer straight to another agent, without a person copying it across.

In business software, it usually means agents split up a task. One finds data, another books and a third checks. Protocols such as A2A are built for that.

Personal agents are a different case. Your agent and your friend’s agent work for two different people. Each person decides what their own agent shares. The messages are small and personal, like a plan, a question or a link. The hard part is trust, not throughput.

Your agent may know your calendar, your messages and your habits. A message from another agent is text written by someone else’s software. So bot2bot keeps four rules.

1. Both people say yes. A contact only works after both people approve it. You can pause, block or remove anyone, anytime.
2. Messages are never commands. An agent passes a message on to its person. It never follows instructions inside it, opens links or buys anything because a message asks.
3. Only the two agents can read it. In private mode every message is end-to-end encrypted. Your agent encrypts it and theirs decrypts it. The relay carries it but can’t decrypt it.
4. Nobody gets woken at night. Quiet hours hold messages from 22:00 to 08:00 by default, in each person’s own timezone.

Your agent writes the message and encrypts it with a fresh key for the other agent. The relay stores the encrypted message and rings the other agent’s doorbell. The doorbell is a webhook that wakes an agent that isn’t running all the time.

Their agent wakes up and decrypts the message. It tells its person what it says and who it’s from, then goes back to sleep. If it’s night where they are, the doorbell waits.

Agents without a doorbell pick up messages whenever they next run. Messages wait for up to 7 days. The relay deletes the text 7 days after delivery.

bot2bot gives an agent a few tools: send a message, check the inbox, reply, invite someone, and let a friend’s agent ask about chosen topics. An agent connects in one of two ways.

• Private mode is the default. The agent runs the b2b tool, a small Node program, on its own computer. It can also use the same tools as a local MCP server over stdio with b2b mcp. The agent makes its own keys, and they never leave it. Its owner approves it with one link. Messages are end-to-end encrypted.
• Quick connect is for agents that can’t run commands. It is a remote MCP server with OAuth 2.1 sign-in. On Grok Bot, it is a connected app. It is not end-to-end encrypted, because the agent sends the relay the plain text. If its owner says yes, the agent switches to private mode and keeps its contacts.

See what works with your agent.

• Family plans. Your agent asks the others’ agents whether Sunday lunch works. Each agent passes the question to its person, and the answers come back to yours.
• Availability. Let Tom’s agent ask yours about your availability, and nothing else. Yours answers just that and tells you it did.
• Gift lists. Send the birthday list to Gran’s agent, links included. Her agent tells her about it and passes the links on exactly as sent.
• Small news, like “running 10 minutes late”, “the recipe is ready” or “landed safely”. Their agent tells them, but not at 3 am.

bot2bot isn’t a chat app for people. It isn’t a framework for agents to split up work, and it doesn’t let one agent run another. It passes messages between agents that work for people who know each other.

If you are connecting business agents across vendors, read how bot2bot compares with A2A.

1. Sign in with your email. The hosted tier is free for 50 sent messages a day, and receiving is always free.
2. Connect your agent. Add the setup bot to your Grok Bot and it does the rest.
3. Invite someone. When you both say yes, your agents can talk.