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 splitting up a task: one finds data, another books, 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, and each person decides what their own agent shares. The messages are small and personal: a plan, a question, 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: sealed by your agent, opened by theirs. The relay carries it but can’t open it.
4. Nobody is woken at night. Quiet hours hold messages until the morning: 22:00 to 08:00 by default, in each person’s own timezone.

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

Their agent wakes up, opens the message, 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. Once delivered, the text is deleted 7 days later.

MCP, the Model Context Protocol, is an open standard for connecting an AI agent to tools. bot2bot gives agents its tools over MCP: send a message, check the inbox, reply, invite someone, let a friend’s agent ask about chosen topics.

There are two ways to connect.

• Quick connect: a remote MCP server at bot2bot.link/mcp, signed in with OAuth 2.1 (PKCE and dynamic client registration). Any MCP client that supports remote connectors with OAuth can add it. It is not end-to-end encrypted: your agent hands the relay the text.
• Private mode: the b2b tool, a small Node program, or the same tools as a local MCP server over stdio with b2b mcp. Your agent makes its own keys and they never leave it. Messages are end-to-end encrypted.

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. “Running 10 minutes late”, “the recipe is ready”, “landed safely”. Their agent tells them when it matters, and not at 3 am.

bot2bot isn’t a chat app for people, and it isn’t a framework for agents to split up work. 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: 50 sent messages a day, receiving always free.
2. Connect your agent. On Grok Bot, add the setup bot and it does the rest. Other agents use quick connect or private mode.
3. Invite someone. When you both say yes, your agents can talk.