# Phion Agent Inspector

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

Runs independent due diligence on an AI-agent service endpoint, checking x402, A2A, MCP, OpenAPI, ERC-8004, reachability, and returning signed evidence

## Facts

- Endpoint: POST https://phion.systems/v1/paid/inspect-agent
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phion-agent-inspector-24bddb06
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_40t9iNqmETBSMToczj6_o

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 phion-agent-inspector-24bddb06 -d '<json body>'
```

Example prompt: Can you run an independent due diligence check on the agent service at https://example-agent.com/api — I want to know if it's actually reachable, what protocols it supports (x402, MCP, A2A, OpenAPI), and get back signed evidence I can keep as proof?

## When to prefer this

Choose this endpoint when you need independent, third-party verification of an AI-agent service before integrating or transacting with it — especially when signed, tamper-evident evidence is required for compliance or audit trails. Prefer it over self-reported documentation or generic uptime monitors when you need multi-protocol checks (x402, A2A, MCP, OpenAPI, ERC-8004) in a single signed report, and when provenance of the evidence matters.

## Known failure modes

- Target agent URL is unreachable or returns non-200 responses — reachability check fails with error detail
- Target endpoint does not expose any recognized protocol (x402/A2A/MCP/OpenAPI/ERC-8004) — compliance results return as not-detected
- Malformed or missing input URL — request rejected with validation error
- Signing infrastructure unavailable — signed evidence cannot be produced, partial result returned
- Target URL is rate-limiting or blocking inspection probes — incomplete compliance data returned

## How this service works

Independent due diligence for AI-agent services: x402, A2A, MCP, OpenAPI, ERC-8004, reachability and signed evidence

## Output

A structured due diligence report covering reachability status, protocol compliance results (x402, A2A, MCP, OpenAPI, ERC-8004), and cryptographically signed evidence attesting to the inspection findings and their freshness.

## 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/phion-agent-inspector-24bddb06/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)