List ring relationships
Backed by the MRR precompute (refreshed every ~2h), so it can sort by relationship_quality (RQ) and PathPower — unlike the live persons list, which only sorts by name or last activity date. Each item is one external person with their embedded primary company, RQ, PathPower, priority signals, AI scores, entity lists and emails.
Internal ring members are excluded. Returns 503 while the precompute has not been built for the tenant yet.
Authorizations
Query Parameters
Page number, 1-indexed. Clamped to >= 1.
Results per page. Clamped to the range 1-100 (values outside are silently capped, not rejected).
Field to sort by. Common values: 'relationship_quality', 'priority_score', 'last_activity_date' (default), 'company_score', 'person_name', 'company_name' — but any column name in the MRR parquet schema works (e.g. 'job_title', 'oldest_signal_created_at'). 'relationship_quality'/'priority_score' are aliases for the underlying 'highest_rq'/'highest_priority_score' columns. An unrecognized value silently falls back to 'last_activity_date' rather than erroring.
Sort order. Valid values: 'asc' (ascending) or 'desc' (descending).
asc, desc Comma-separated integers (1-3) to filter by exact match against each person's highest Relationship Quality (RQ) score across the ring.
Comma-separated integers (1-3) to filter by exact match against each person's highest Priority Score across the ring.
Filter by the person's primary company's AI score (company_score). Exclusive bound: matches scores strictly greater than this value (not >=).
Filter by the person's primary company's AI score (company_score). Exclusive bound: matches scores strictly less than this value (not <=).