Match profile editor — how you get matched
The explainability seam made editable: the facts the matching engine ranks providers against (vertical, revenue band, team size, state) in a 'How you get matched' editor on Discover. Full-state save — engine-owned tiers/scores pass through untouched so the write can't clobber them.
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: GET/PUT /api/v1/match/profile.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Part of the 'discover' module.
- Who can use it
- RBAC: match.profile.read / match.profile.write.
- The API behind it
GET/PUT /api/v1/match/profile- Where it lives
- /discover
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.