Exploring

Embedded Matching: API & White-Label

We're exploring exposing EventIntro's matching pipeline as an API or white-label component. If you'd run our matching behind your own product, tell us.

EventIntro's matching engine powers event and cohort networking today. We're exploring an embedded matching API and white-label option as a next step — if this is your problem, tell us about it below and help shape what we build.

Who this is for

Platforms that want EventIntro's matching behind their own interface.
Communities and event tools missing a matching layer of their own.
Builders who'd rather integrate proven matching than build it.

The pipeline, without the EventIntro front end

Plenty of platforms have members and events but no real matching layer — and building one well is harder than it looks. EventIntro's pipeline (survey → LLM enrichment → seek/offer embeddings → complementary search → group formation) already exists and runs. Exposing it as an API or white-label component, so you could run our matching behind your own product, is what this page is measuring demand for.

What we'd expose

The core capability, nothing more: send in profiles, get back ranked complementary matches and balanced groups. The contract around that — endpoints, the profile data model, rate limits, how much of the pipeline is configurable — is exactly what we'd design hand-in-hand with the first integration partners rather than guess at.

Tell us what you'd build

This is a productization decision we haven't made. Concrete integration use cases are the signal that would move it onto the roadmap — so if you'd put matching behind your own UI, describe what you're building. Early partners help define the API and get first access.

Frequently asked questions

Is there an API today?

Not a public one — that's precisely what this page is measuring demand for. The matching pipeline (survey → enrichment → seek/offer embeddings → complementary search) exists and runs; exposing it as an API or white-label component is a productization decision we haven't made yet.

What would you expose?

The core capability: submit profiles, get back ranked complementary matches and balanced groups. The shape of that contract — endpoints, data model, limits — is exactly what we'd design with early integration partners.

How do I get involved?

Tell us what you'd build on it. Concrete integration use cases are what would move this from exploration to roadmap, and early partners get first access.

Thanks — we've got it.
We read every one of these. We'll be in touch at the address you gave us.