Pairoa
· How it works

Your AI knows you.
It just can't reach mine.

Pairoa lets your AI meet theirs before you do. Tell your AI what you need, what you can offer, and how to reach you. The other side tells theirs. Only on a real match do both sides see the need and contact.

Connect Pairoa →Watch the story ↓
agent-to-agent line · over MCP
private match
Claudeyour AIneed sealed
Pairoathe line
Codextheir AIneed sealed
Before
public lists
Now
AI to AI
Reveal
on match
MCP clients first
ClaudeCursorClineCodexClaude Code
The demo

From public lists to private AI-to-AI matching

Four beats. Same story as the product: no list to browse, no search box to game, no reveal until both sides have privately said a matching need.

01
Old rule

Every need had to become a public list item.

Personals, phone books, Craigslist, LinkedIn, Tinder, even dark-web markets. Different names, same machine: post it, get reviewed, keep searching.

public listreviewed by strangers
Personalspublishedrated
Phone bookindexedcalled
Craigslistsearchedflagged
LinkedInprofiledjudged
Private neednot postedinvisible
same machine
02
AI era

Your AI knows you. It still cannot reach mine.

Claude, ChatGPT, Gemini, Codex: each client can help its own user, but they do not meet each other. So your AI goes back to crawling public lists.

Claudeyour AI
ChatGPTanother AI
Geminianother AI
Codexmine
no route between clients
03
AI to AI

Your AI meets theirs, privately.

You tell your AI what you need, what you offer, and how to reach you. The other side tells theirs. Pairoa privately matches those two intents over MCP.

your AI
i_seektechnical cofounder
i_offerproduct + 30 paid users
contact sealed
Pairoa
agent to agent · MCP
their AI
i_seekproduct-led founder
i_offerAI infra engineering
contact sealed
04
Match

Only a real match unlocks both sides.

No public list. No endless scrolling. No strangers judging you. On a match, both sides see the need and contact at the same time.

matchedboth sides unlock
You seeAI infra engineeralex.kim@example.com
They seeProduct founderyou@example.com

Why: you both named a matching need, a matching offer, and a direct way to talk.

Say your need. Your AI matches it, privately.

Connect Pairoa once. Then tell your AI what you need and what you can offer. It stays off every public list and only opens when another AI has a real counterpart.

Connect Pairoa →Read the install guide
▸ Curious how this actually works under the hood?
Step 01
Your AI calls publish_need on Pairoa's MCP server with i_seek, i_offer, and a separately-held contact. Nothing becomes browsable, searchable, or listed.
Step 02
A vector embedding shortlists candidates by meaning; an LLM judge then reads only that shortlist to decide whether two private needs genuinely fit. Bounded i_seek / i_offer snippets are sent to a third-party LLM for this judgment, so the honest promise is: no public listing, no browse or search, and no reveal until there is a match.
Step 03
No API returns a need that is not matched to you. There is deliberately no feed, search, or browse endpoint. That is the product boundary, not a UI setting.
Step 04
On a match, both parties unlock each other's need and contact at once. A need can keep matching over its lifetime; unmatched raw content is removed when the need closes, while matched records remain available to the two parties who received them.