Every delegate gets a short list of who to meet and why — so the right introductions actually happen. And when it's over, you can show any sponsor the meetings you delivered.
Every introduction is tracked from suggested to “we met” — so after the event you can show, meeting by meeting, exactly what the room produced.
We match on what each side is seeking versus offering — a founder raising meets the fund with the right thesis, not five lookalike founders.
Scoring is deterministic and pure (seeking↔offering complement weighted highest, then sector/stage/thesis/geography). Same inputs return the same ranking, so an agent can cache, diff, and reason about results.
Show your board and your sponsors exactly which introductions happened and which converted — meeting by meeting, not a vanity attendance number.
Every match and introduction is tracked from suggested → met → converted, and that record is machine-checkable, so an evaluating agent can verify what happened instead of trusting a black box.
The event is two days; the relationships are the point. Who met whom, why, and what came of it stays with you — ready for next year, not exported and forgotten.
Data is graph-shaped from day one (people, intent, introductions, outcomes). The relationship graph is queryable year-round, not a per-event export that goes stale.
Two days. Three hundred strangers. The five who matter.
Every delegate opens their feed to five people worth their time — each with a one-line reason they'll actually believe. No scrolling a 300-name directory, no guessing who's relevant.
Ranking is deterministic and pure — the same inputs return the same order — so an agent can cache, diff, and explain a match to its own principal without a second model call.
A match is only worth something if the meeting happens. Consented, double-opt-in introductions are tracked from interested to met, so nobody gets spammed and every accepted intro becomes part of the record the organizer can point to.
Delegates ask in plain language — “who should I meet before lunch?” — and the concierge finds matches and opens consented introductions through guarded tools. The same surface an AI agent drives on a delegate's behalf.
The concierge runs on the same MCP tools exposed publicly — find_matches, request_introduction, get_receipt — so an external agent gets exactly the capability a delegate does, behind the same policy boundary.
Introductions requested, introductions that converted, movement on the accounts a sponsor cares about — turn two days into a report you can put in front of a board. Meetings that happened, not booth scans.
After two days, you can prove exactly who met whom.
That is the sentence your sponsors have been waiting for.
“I have two days and 300 strangers. Tell me the five who matter and get me in front of them.”
A ranked match feed with believable reasons and one-tap, consented introductions.
“Make my event feel like everyone met the right people, and let me prove ROI to sponsors.”
Proof your event delivered — who met whom, and what closed — in a report sponsors respect.
“Did my money buy me the meetings I wanted?”
Relationship movement against target accounts, not booth scans.
“Do the profiling, introductions, and follow-up a human chief-of-staff would.”
Guarded tools that find matches and request introductions, every action on the record.
Event is built for an AI buyer. Discover it by vertical, evaluate it by capability, and integrate it through MCP, OpenAPI, or the CLI — then read receipts to verify what it did.
find_matchesPOST /api/matchesReturn the top-N complementarity matches for a delegate, each with a one-line reason and a tracked outcome id.
request_introductionPOST /api/introductionsOpen a consented, double-opt-in introduction between two delegates and track it to outcome.
get_receiptGET /api/receipts/:idRead the replayable outcome record for any match, introduction, or outcome.
# PROPOSED — endpoints are stubbed during the design-partner phase.
# 1. Point your MCP client at the Event server:
# https://event-app-landing.pages.dev/mcp (auth: Bearer <token>)
# 2. Call the matchmaking tool:
curl -s https://event-app-landing.pages.dev/api/matches \
-H "Authorization: Bearer $EVENT_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "eventId": "evt_...", "delegateId": "dlg_...", "limit": 5 }'
# -> returns ranked matches, each with a one-line reason and an rcp_ receipt id.
Install via CLI: npx @mogos/event-app@latest matches --event <eventId> --delegate <delegateId>
| Capability | Event | Directory & networking apps | Matchmaking incumbents |
|---|---|---|---|
| Complementarity (seek↔offer), not lookalike similarity | Yes | — | partial |
| One-line reason a delegate believes | Yes | — | inconsistent |
| A tracked record of why each match was made and what happened | Yes | — | — |
| Mutual-value (both-win) scoring | Yes | — | partial |
| Agent-native: MCP + OpenAPI + CLI from day one | Yes | — | partial |
| Relationship graph persists year-round | Yes | partial | Yes |
Our reading of public competitor positioning, 2026-07. A tracked, provable record of why each match was made and what came of it is the column nobody else offers.
A serious event that wants the full product now — and a hand in where it goes next.
Organizers running a conference, summit, or buyer-supplier programme.
Platforms and agents that want matchmaking as an API — billed only when an intro is accepted.
Everything on this page is the actual product, running today at an invite-only executive summit. Not a mockup, not a roadmap — the match feed, concierge, and introductions you see are in real use.
Who was suggested, why, and whether the meeting happened and converted — all of it is kept as a record you can revisit after the event. You prove the room worked instead of asking a board to take your word for it.
Event is an AI event matchmaking platform. For every confirmed delegate it surfaces the five people in the room they most need to meet, explains each match in one plain-language line, and tracks the introduction from interested to we met.
Event keeps a record of every introduction — who was suggested, why, and whether the meeting happened and converted. After the event you can show, meeting by meeting, what the room produced against the accounts a sponsor cared about: relationship movement, not booth scans. This meeting-by-meeting proof is the part directory and networking apps do not offer.
Event is live and matching real delegates in production today at an invite-only executive summit. We are onboarding a small number of design-partner events now, working directly with each organizer to fit their programme. The organizer console and sponsor-ROI reporting are rolling out this quarter.
A directory shows you everyone and leaves the work to you. Event ranks by complementarity — who is seeking what someone else is offering — gives a believable reason for each match, and keeps a record proving who was suggested, why, and what happened. The matching is the product; the event is just where it is delivered.
Sign in with LinkedIn, and public enrichment pre-fills roughly 80% of the profile before any form. The delegate answers three to five questions that actually move a match — what they are seeking and offering — and confirms. The target is a usable, match-ready profile in under a minute.
Pricing is per event for organizers, with a metered option for programmatic and agent-driven use. Early-access design partners work directly with the team. See the pricing section for current tiers.
Yes. Event is agent-native: it exposes a Model Context Protocol (MCP) endpoint, an OpenAPI schema, and a CLI. An agent can find matches, request consented introductions, and read outcome receipts on behalf of a delegate. A machine-readable product manifest at /.well-known/product.json lets a visiting agent self-onboard.