# Data Egress Preflight

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

Inspects outbound agent payloads for secrets, unsafe destinations, and size limits before they are sent to an external tool or API

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/data-egress-preflight
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/data-egress-preflight-5cbd59f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QM7XSSlFt9Jbiy3QJFANz

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 data-egress-preflight-5cbd59f6 -d '<json body>'
```

Example prompt: Before you send that POST body to the Stripe API, run a data egress preflight on it — check the payload for any exposed secrets or API keys, make sure the destination is safe, and confirm the size is within policy.

## When to prefer this

Use this endpoint when an AI agent is about to send data to an external tool or API and you need a lightweight, pre-transmission safety gate — especially when the payload may contain user data, secrets, or credentials that should not leave the system. Prefer this over manual auditing or post-hoc logging when you need a real-time block/allow decision before egress occurs.

## Known failure modes

- Malformed or empty input schema may return a validation error
- Destination URL not parseable results in a rejection
- False positives on secret detection for non-sensitive patterns resembling keys
- Payload too large to inspect may time out or be rejected
- Ambiguous policy configuration may yield inconsistent verdicts

## How this service works

Inspect payload, destination, secrets and size before an agent sends data to a tool or API

## Output

Returns a structured preflight decision indicating whether the egress is permitted or blocked, along with a breakdown of any detected secrets, policy violations, destination safety issues, or size limit breaches found in the payload.

## 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/data-egress-preflight-5cbd59f6/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)