What this is

Performix's HTTP + MCP surface. All routes are auth-protected (Clerk); production is not public.

Conventions

• Routes: src/app/api/<namespace>/<verb>/route.ts; team-scoped methods under /api/teams/{teamId}/*.
• Auth: Clerk session/authorization on every call.

Endpoints

Capability	REST	MCP	Returns
CAMS binding-constraint diagnostic	POST /diagnose	—	CAMS scores + the single binding constraint (UI: /diagnose)
Executive Readout	POST /api/teams/{teamId}/executive-readout	executive_readout	framed competency-rollup + perception-gap
Interpretability Rules	POST /api/teams/{teamId}/interpretability-rules	interpretability_rules	"why this nudge / why this flag" over a precomputed prediction
Conformal-Interval Confidence Gating	POST /api/teams/{teamId}/conformal-gating	conformal_gating	decide vs. abstain on prediction uncertainty
Coaching Door	UI (Coaching Door)	—	simulated-practice scoring + behavioral-signal nudges

Full generated reference

Generated from docs/capability-manifest.json → reference-apis.generated.md / reference-mcp.generated.md. Regenerate with node ~/devplane/scripts/gen-product-reference.mjs ..

Honest scope

/diagnose is real in prod; the team-scoped executive methods are shipped; the Coaching Door is a UI surface. Performix consumes upstream toolbox/Principia services — these endpoints assume those are reachable.

See also

Getting Started · Concepts · Trust & Confidence