# x402 v2 Router

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

Selects a compatible x402 v2 payment requirement for an agent without exposing or transmitting private keys

## Facts

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

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 x402-v2-router-e5ff75ec -d '<json body>'
```

Example prompt: I need to find a compatible x402 v2 payment requirement for this API call — can you route it through the x402 v2 router so my agent picks the right option without exposing any private keys?

## When to prefer this

Use this endpoint when an agent needs to automatically select a compatible x402 v2 payment requirement before calling a paid API, especially when security is a priority and private keys must never leave the agent's secure context. Prefer this over manual payment negotiation or generic payment routers when you need deterministic x402 v2 compatibility matching with a signed, trustworthy selection outcome.

## Known failure modes

- No compatible x402 v2 requirement found for the given input — returns an error or empty selection
- Malformed or missing input schema fields cause a validation error
- The target payment requirement version is not v2 — incompatible and not matched
- Service returns an error if the request exceeds rate limits or the $0.003 USDC fee is not settled

## How this service works

Select an exactly compatible x402 v2 requirement without receiving private keys

## Output

A selected, exactly compatible x402 v2 payment requirement object that the calling agent can use to satisfy the payment gate of a target API, without any private key material being transmitted or exposed in the process.

## 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/x402-v2-router-e5ff75ec/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)