# Counterparty Risk Preflight

> Counterparty Risk Preflight is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).

Makes a deterministic policy decision on whether to proceed with a counterparty transaction based on supplied reputation evidence and transaction limits

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/counterparty-risk-preflight?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/counterparty-risk-preflight-c9cec7fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Du23kE4g7IGwWzNrxBa8x

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 counterparty-risk-preflight-c9cec7fd -d '<json body>'
```

Example prompt: Before I send 500 USDC to this counterparty agent with the reputation evidence I've gathered, run a preflight risk check to get a policy decision on whether this transaction is within acceptable limits and the entity is trustworthy enough to proceed.

## When to prefer this

Use this endpoint when an agent needs a deterministic, policy-bound go/no-go decision before transacting with an unknown or partially known counterparty, especially in agentic or multi-agent contexts where automated trust screening is required. Prefer this over general reputation endpoints when you need a hard decision rather than a probabilistic score, and when transaction limit enforcement is part of the policy.

## Known failure modes

- Insufficient reputation evidence provided — decision cannot be made with confidence
- Transaction limit parameters missing or malformed — returns validation error
- Counterparty identifier not recognized or unresolvable
- Policy conflict detected — ambiguous outcome returned with explanation
- API returns 402 if payment is not attached or insufficient

## How this service works

Deterministic counterparty policy decision using supplied reputation evidence and transaction limits

## Output

A deterministic policy decision (approve or reject) on the counterparty, including a verdict, decision rationale, and any applicable limit or evidence coverage signals that informed the decision.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/counterparty-risk-preflight-c9cec7fd/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)