---
title: "Mpc Results"
method: GET
path: "/api/outbound/mpc-results"
tags: ["Outbound", "outbound"]
---

# Mpc Results

`GET /api/outbound/mpc-results`

## Request

- Base URL: `https://api.ruzora.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.ruzora.com/api/outbound/mpc-results`
- Auth: none declared

Read back what MPC actually did. Board Round 2 #26, tech design M4-15.

Without this the data accumulates in mpc_pitches and nobody can look at
it: rows, and no answer.

Read in this order:
  1. rank_distribution — is the matcher better than chance, and does
     anyone ever click past rank 2? This settles the 3-vs-5 question
     without splitting traffic.
  2. by_arm.avg_cards — the VALIDITY check. If the challenger arm
     cannot fill its card count, a null result is the harness's fault.
  3. guardrails — bounces and opt-outs. ruzora.com carries every
     outbound channel, so this stops the experiment on its own.
  4. coverage — PRD §6.1's independent kill rule: below 50% the
     assignment logic is broken however good the reply rate looks.

Read-only. No auth, matching the ticks above: it exposes counts and
rates, never a candidate name, a company, or an email address.

## Query parameters

- `days` integer

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/ruzora/apis/ruzora-candidate-crm-api.md) · [All operations](https://skmtc.dev/ruzora/apis/ruzora-candidate-crm-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ruzora/apis/ruzora-candidate-crm-api/revisions/f9b8223f3ac4?raw)