Matchmaking Intelligence Platform

Level 1 · decision layer · deterministic How it works ↗

Ingest an entity

Raw identity is sent to the gateway only; it's tokenized/de-identified before anything else ever sees it.

Recently ingested (this browser only)

Labels are kept in your browser's local storage for convenience only -- the backend never stores or returns raw identity after ingest.

Bulk ingest from CSV

Columns (case-insensitive, only name required): name, org, email, kind, industry, stage, profile, needs, capabilities, preferences, opportunity. A row's own kind column (if present) overrides the default kind below -- useful for a mixed file. Parsed and sent as one batch; each row runs the same PII pipeline as a single ingest, and one bad row won't lose the rest.

Run a match

Batch match (many-to-many)

Runs the same match once per requester below -- retrieval already scopes each call to the opposite-kind pool in the tenant, so a list of startups against a list of funders is just "run match for every startup"; there's no separate many-to-many primitive to configure.

View a previously saved run

Re-load a results CSV downloaded above to view it again, without calling the API.

Interpret an instruction

Rules parser first, zero model calls for simple patterns (prefer/avoid/exclude/only show/focus on X). Nothing activates until you confirm.

Compare snapshots

Record feedback

Feedback is only accepted for a request_id with a delivered match -- run a match first.

Entity availability