# Conflict Resolution

> Conflict Resolution is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Selects among conflicting agent results using explicit, policy-driven arbitration to resolve ambiguity

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/conflict-resolution
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/conflict-resolution-c416d811
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ikvr6p10_PCSGhQ1J_8JO

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 conflict-resolution-c416d811 -d '<json body>'
```

Example prompt: I have three agents that returned conflicting answers about the same question — can you apply my explicit resolution policy to pick the right one and explain why it won?

## When to prefer this

Use this endpoint when your agent orchestration layer produces multiple conflicting results and you need a deterministic, policy-driven arbitration step rather than ad hoc LLM judgment. Prefer this over asking a general-purpose model to 'pick the best answer' when auditability, explicit policy compliance, or trust levels matter. Especially valuable in multi-agent pipelines where different agents may have different data sources or reliability levels.

## Known failure modes

- No conflict provided — returns error if fewer than two candidate results are submitted
- Policy not recognized or malformed — returns validation error if the resolution policy is undefined or invalid
- All candidates equally invalid under policy — may return an unresolvable conflict error
- Schema mismatch — bare input schema may cause rejection if required fields are missing
- Payment failure — x402 payment not completed results in 402 response

## How this service works

Select among conflicting results using explicit policy

## Output

Returns the winning result selected from the conflicting candidates along with the policy rationale explaining why that result was chosen over the others. Includes the resolved output and decision metadata.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/conflict-resolution-c416d811/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)