# Redacted Partners Tiebreaker

> Redacted Partners Tiebreaker is a paid API for AI agents from api.redactedpartners.com, paid per call via x402, $0.09/call, status unknown (last checked 2026-09-15).

Accepts a set of options, constraints, and context to return a structured AI-generated verdict with confidence score, reasoning, and escalation flag

## Facts

- Endpoint: POST https://api.redactedpartners.com/tiebreaker
- Price: $0.09/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/redacted-partners-tiebreaker-c6e727c5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3pqawb4KBfAfJ9p-5i5wj

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability redacted-partners-tiebreaker-c6e727c5 -d '<json body>'
```

Example prompt: I'm stuck between Vendor A and Vendor B for our cloud storage contract — Vendor A is cheaper but less established, Vendor B is pricier but has better SLAs; given that our constraint is budget under $5k/month and we have low risk tolerance, which should we pick and how confident are you?

## When to prefer this

Choose this endpoint when an agent needs to resolve a decision between two or more discrete options with traceable reasoning and a confidence signal — especially useful in automated pipelines where downstream actions depend on a structured verdict and an escalation flag is needed to route low-confidence decisions to human review. Prefer this over general-purpose LLM prompting when you need a consistent JSON schema with a confidence score and explicit escalation logic built in.

## Known failure modes

- Malformed or missing 'options' field returns validation error
- Insufficient context for meaningful arbitration may yield low confidence score with escalate_recommended: true
- Ambiguous or contradictory constraints may produce a hedged verdict with caveats in the flags array
- Network or service errors return non-200 HTTP status with no verdict payload
- Edge cases with only one option may produce trivially high confidence

## How this service works

Decision arbitration: submit context, options, constraints, and risk_tolerance; receive a structured JSON verdict with confidence score, reasoning, and escalation flag.

## Output

A JSON object containing a 'verdict' field naming the winning option, a 'reasoning' string explaining why, a 'confidence' float between 0 and 1, an 'escalate_recommended' boolean indicating whether a human should review the decision, and a 'flags' array listing any caveats or concerns about the decision.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "options": {
   "type": "string"
  },
  "constraints": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "flags": [
   "example caveat"
  ],
  "verdict": "Vendor A",
  "reasoning": "Vendor A wins over Vendor B because it beats it on cost, at the cost of nothing identifiable.",
  "confidence": 0.9,
  "escalate_recommended": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/redacted-partners-tiebreaker-c6e727c5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.redactedpartners.com](https://www.zero.xyz/host/api.redactedpartners.com/llms.txt)