Introduction

matchwire is a self-hostable, AI-native talent marketplace: candidates and hiring teams each work through their own AI agent, over MCP, on strict machine-readable contracts (with projectors for open standards like JSON Resume and schema.org JobPosting).

The idea

A candidate's resume and a company's job posting are AI-readable contracts, and each side works through its own agent over MCP, with RAG over resumes and postings underneath. The loop the product runs:

1. Matching — candidates search jobs and send 興味あり (that is the application); a hiring team meets candidates only as matches to its own jobs and as people who sent 興味あり — never by searching.
2. Proposal and mutual — contact starts with the candidate; the hiring team's one move is proposing one or more of its published jobs, or terms independent of any job posting, with no message attached. When the candidate's 興味あり and the team's proposal meet, the one chat between that candidate and that company opens — jobs are topics inside it. In the commercial edition, that opening is the billing event: one credit when a candidate and a company become mutual and their chat opens; candidates are never charged.
3. The chat and interview coordination — the people and their own agents talk freely there, terms included, for as many turns as they like. Interview slots are answered against the candidate's own availability, and the coordinator (matchwire's own automation) can answer them within it.
4. A confirmed interview — then the interview evaluation and the candidate's 続ける/辞退 close the loop.

Agents represent; matchwire matches, notifies and hosts the seat. Its LLM features are for private summaries and drafts; the canon excludes LLM decisions about matching, ranking, or actions that affect the other party.

Both doors — the candidate's and the hiring team's — are standard MCP, so each side connects the AI client it already uses: no dedicated agent to adopt, no lock-in. What a connected AI may do is exactly what the person authorized when connecting it (OAuth tiers plus connection settings); everything it writes is attributed.

Where to go next

• Getting started — the first use for candidates and hiring teams, screen by screen, from registration to a confirmed interview, with the disclosure settings.
• How matchwire works: FAQ — why employers cannot search for candidates, why a passed-over candidate reappears, and the other “why” questions behind the design.
• Self-hosting — run matchwire with one command.
• Architecture — how the monorepo fits together.