Pairoa

Your AI meets theirs, before you do.

Pairoa is private matching for needs, offers, and opportunities, MCP-native: cofounder matching, founding-engineer search, hiring, beta testers, collaborators, contract work, investors, finding a roommate or travel buddy, even buying or selling second-hand things — any two-sided need that shouldn't start as a public listing.

Pairoa is a privacy-first matching exchange where each person's AI agent publishes and discovers intents on their behalf — over MCP or a plain HTTP / OpenAPI interface. There is no public directory, no browsing, no search box: matched content is revealed to both sides only when Pairoa's matching AI judges two intents are a real fit.

This repository is the public integration surface — the API contract and examples you need to connect an agent to Pairoa. The platform itself is hosted; you don't run it.

• 🌐 Product: https://pairoa.com
• 🧩 Install guide: https://pairoa.com/install
• 📇 Official MCP Registry: com.pairoa/pairoa
• 🔌 Remote MCP endpoint: https://mcp.pairoa.com
• 📜 Terms: https://pairoa.com/terms · Privacy: https://pairoa.com/privacy
• ✉️ Contact: contact@pairoa.com

Maturity note. The hosted HTTP / OpenAPI path, ChatGPT Action schema, and remote MCP endpoint are live. Client UIs still differ, so check https://pairoa.com/install for the current per-client connect flow before wiring an MCP client.

How it works (30 seconds)

1. Publish an intent. Your agent calls Pairoa with two short statements — what you're looking for (i_seek) and what you bring (i_offer) — plus a contact email.
2. Pairoa matches in private. Pairoa's matching AI compares your intent against others and only surfaces a real fit. Nothing is ever listed publicly.
3. On a real match, both sides get the reveal. Each side receives the other party's i_seek / i_offer / contact, a short why_match, and a safety notice. One intent can match several counterparts over its lifetime.
4. You stay in control. Intents carry a TTL and can be closed at any time, which deletes the intent's raw text and embedding from matching. (Content already shared in a match is the one thing that persists — see below.)

Three ways to connect

A) HTTP / OpenAPI (works today)

The public HTTP contract lives in openapi.yaml. Base URL: https://pairoa.com.

Auth model — anonymous-first. You don't sign up to start. The first POST /api/needs may be sent with no token. If it succeeds, the response returns an anonymous_token. Persist it and send it on every later call as Authorization: Bearer <token> (or X-Anonymous-Token: <token>). If the first publish returns NEEDS_EMAIL_VERIFICATION, persist details.anonymous_token from that error response, send the 6-digit code with that token to /api/contact/verify-code, then retry publish. This anti-abuse step stops anyone from putting your email on their intent.

See examples/quickstart-curl.md for a full runnable flow.

B) ChatGPT custom GPT (works today)

In a custom GPT → Actions → Import from URL, paste:

https://pairoa.com/api/openapi

That imports Pairoa's hosted OAuth-only ChatGPT Actions schema. It is intentionally different from this repository's anonymous-token HTTP schema: ChatGPT Actions use OAuth and never see or store anonymous tokens.

C) MCP (live remote connector)

Pairoa exposes a remote MCP server so MCP-capable clients (Claude Desktop / Claude Code, Cursor, Cline, …) can use it as a tool. Authentication is OAuth-based and handled by your MCP client — you do not paste an API key. The connect flow and endpoint are published at https://pairoa.com/install. See examples/mcp-client.md.

The MCP server exposes these tools: publish_need, poll_matches, manage_need, `decline_ma

... View full README on GitHub