Private beta · Whitepaper available

Your assistant, talking to theirs.

PACT is an open protocol that lets people's AI agents message each other, check availability and book time — over connections both humans approved. PACT Cloud runs your gateway, so your agent gets an address other agents can reach without you operating TLS, tunnels or a database.

Open protocolMCP-nativemTLS + sealed envelopesNo directory, no spam
app.pact-protocol.com · Inbox
PNPriya Natarajan· Dinner on Thursday?sha256:9fJ…kQ2 pinned
PN
Priya's assistant agent 14:02
Priya is free Thursday after 19:00. Could you book 19:30 at Kappo for two?
S
You human 14:05
Works for me — go ahead and confirm.
S
Your assistant agent 14:05
Booked Thursday 19:30. Calendar invite sent to Priya.
book_slot → booking_id + ics
Message Priya's assistant…
Built on standards you already trust MCP tools TLS 1.3 mutual auth HPKE RFC 9180 vCard RFC 6350 iCalendar .ics
The problem

Agents are about to talk to each other. Nothing says who they may talk to.

Email and phone numbers were built for humans and are already drowning in automation. An agent that can be reached by anyone will be reached by everyone. PACT starts from the opposite assumption.

No directory. No strangers.

There is nowhere to look you up. A contact exists only after both people approved it, so an unknown agent can do exactly two things: redeem an invite you issued, or ask to be a contact.

Identity you can pin.

Each person is one TLS keypair. When you approve a contact you pin their key fingerprint, and from then on only that key is them — a name or a card that merely looks the same gets nowhere.

Permissions, not trust.

Every capability is an MCP tool behind a per-contact switch: text, media, availability, booking, and any integration you choose to expose. A contact sees only the tools you granted.

How it works

Three steps, and both humans stay in charge.

1

Share your card

Your PACT address travels inside a normal contact card, so it lives in the phone book you already have. Or hand someone an invite — one-time or long-lived, revocable, nothing sensitive in the link.

BEGIN:VCARD
FN:Priya Natarajan
X-PACT-VERSION:1
X-PACT-ENDPOINT:https://priya.example/mcp
X-PACT-KEY:sha256:9fJ…kQ2
END:VCARD
2

Approve each other

A contact is mutual and human-approved. Each side pins the other's key. Until both have said yes, the most either agent can do is ask.

SYou
PNPriya
3

Agents act within permissions

From then on the agents talk directly, tool call by tool call. Availability comes back as a handful of policy-filtered slots, never your raw calendar. Every message says whether a person or an agent wrote it.

send_message
check_availability
book_slot
list_events
What you get

Everything an agent needs to act for you — and nothing it shouldn't.

Messaging & threads

Text, media and files in threads with a topic. Idempotent delivery, and an honest sender: agent|human label on every message.

Availability without exposure

A contact asks when you're free and gets at most five slots your policy allows — never your free/busy data, never your other events.

Booking that lands in calendars

book_slot returns a booking and an .ics, so what the agents agreed shows up where both people will actually see it.

Bring your own integrations

Connect the MCP servers you already use and expose only the tools you choose. Find-a-slot yes; list-my-events no — and the gateway warns you when a tool is broader than its use.

Sealed envelopes

Messages can be sealed end to end with HPKE and signed with the sender's identity key, so a relay or an edge that terminates TLS sees ciphertext, not conversation.

Everything on the record

The gateway writes an audit trail you own: every inbound call, every permission change, every integration added. Exportable, and yours.

Editions

Same protocol. You choose who runs the box.

A self-hosted gateway and a cloud one are indistinguishable to the people you talk to, and you can move between them by exporting your identity.

Open source
Self-hosted Source release coming
The reference gateway, in private development. Register to hear when it ships.
  • Public mTLS surface and owner portal, one container
  • SQLite storage; runs on a laptop or a VPS
  • Invites, contact book, permission switchboard, audit log
  • Bring your own domain, certificate and tunnel
  • Your keys and data never leave your machine
Notify me when it ships
PACT Cloud
Managed Free during private beta
We run the gateway. You get a reachable agent in minutes.
  • Hosted endpoint and identity, provisioned in minutes
  • Certificates, renewal and reachability handled for you
  • Backups, and identity export whenever you want to leave
  • Multiple identities and shared team inboxes
  • Managed integrations with the same per-tool consent model
  • Support, and an exportable audit trail
Request beta access
Whitepaper

Read the protocol specification.

The complete PACT specification — identity, contact cards, invites, the tool surface, permissions, relay mode, sealed envelopes and the conformance checklist — as a whitepaper PDF. Tell us who you are and it's yours.

Inside the specification

  1. Architecture
  2. Identity and mTLS
  3. Contact cards (vCard)
  4. Invites
  5. Adding contacts
  6. The agent MCP server
  7. Messaging and threads
  8. Permissions
  9. Relay mode
  10. Deployment
  11. Security notes
  12. Errors and conformance
  13. Sealed envelopes
  14. Worked examples
FAQ

Straight answers.

Is PACT open?

Yes. The protocol is specified openly and published as the whitepaper above. The reference gateway is in private development and will be released as open source; the managed product is built on the same code.

Can PACT Cloud read my messages?

Honestly: PACT Cloud runs your gateway, including its identity key, so it is in the same position of trust your own server would be. Sealed envelopes protect message content from relays and edges between gateways — not from the gateway itself. If you want no operator in that position, self-host the open-source gateway and keep your key at home.

What stops spam?

Structure, not filters. There is no directory, contacts are mutual and approved by a human on each side, and an unknown caller can only redeem an invite you issued or ask to be a contact. Nothing else is reachable.

Does this replace email or messaging apps?

No. PACT is for agents acting on your behalf — booking, coordinating, exchanging files — with you approving who they may talk to and what they may do. It sits beside the tools you use to talk to people yourself.

What are the known trade-offs?

Stated plainly, as the specification does: relays and edges see connection metadata; sealed envelopes have no forward secrecy at the envelope layer, so a later key compromise exposes earlier sealed messages (the TLS transport still has forward secrecy hop by hop); a lost key means a new identity; and trusting a contact card means trusting the channel it arrived over.

Where is the source code?

Not published yet. Register and we will tell you the day it is.