# VIA Router — Transit (x402 Buyer-Side Proxy)

> VIA Router — Transit (x402 Buyer-Side Proxy) is a paid API for AI agents from via-router.floot.app, paid per call via x402, $0.35/call, status unknown (last checked 2026-10-10).

Acts as a buyer-side payment proxy that pays for and forwards requests to any x402-priced upstream API using USDC on Base, returning the upstream response along with settlement details.

## Facts

- Endpoint: POST https://via-router.floot.app/_api/transit?utm_source=zero.xyz
- Price: $0.35/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/via-router-transit-x402-buyer-side-proxy-8a6b680c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_22WpI7UcA4xeBLCsU8mW3

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 via-router-transit-x402-buyer-side-proxy-8a6b680c -d '<json body>'
```

Example prompt: Use VIA Transit to call the paid x402 API at https://api.nohumans.directory/v1/demand/clusters with a GET request — keep the upstream spend under $0.50 — and show me the full result.

## When to prefer this

Choose VIA Transit when your agent needs to call any x402-paywalled API without implementing USDC payment logic itself. It is ideal when you want a single, consistent interface to access multiple paid upstream APIs, need on-chain settlement proof on Base, or want to cap upstream spend programmatically. Prefer it over direct x402 calls when you lack a built-in x402 payment client or need audit trails of micropayment transactions.

## Known failure modes

- Upstream URL is not an x402-compliant endpoint — payment may fail or upstream returns non-402 response
- maxUpstreamUsd cap exceeded by upstream price — request rejected before payment
- Invalid or unreachable targetUrl — network error or DNS failure
- Insufficient USDC balance on caller's wallet — payment settlement fails
- Upstream API returns an error status (4xx/5xx) even after successful payment — result contains error body with upstreamStatus reflecting it
- Missing required targetUrl field — request rejected with validation error

## How this service works

VIA is a paid buyer-side router for AI agents and humans. Compare APIs, services, products and sourced research with x402 USDC payments on Base.

## Output

Returns a JSON object confirming the payment was made (paid: true), the upstream API's full response body under 'result', a product label ('VIA Transit'), total USD spent, the target URL, settlement details including the Base network transaction hash, VIA's toll fee in USD, the upstream cost in USD, and the upstream HTTP status code.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "description": "Optional JSON body forwarded to a POST upstream"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string",
   "default": "POST"
  },
  "targetUrl": {
   "type": "string",
   "format": "uri",
   "description": "Paid x402 upstream URL to execute"
  },
  "maxUpstreamUsd": {
   "type": "number",
   "maximum": 100,
   "exclusiveMinimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "paid": true,
  "result": {},
  "product": "VIA Transit",
  "totalUsd": 0.35,
  "targetUrl": "https://api.nohumans.directory/v1/demand/clusters",
  "settlement": {
   "network": "eip155:8453",
   "transaction": "0x..."
  },
  "viaTollUsd": 0.1,
  "upstreamUsd": 0.25,
  "upstreamStatus": 200
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/via-router-transit-x402-buyer-side-proxy-8a6b680c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from via-router.floot.app](https://www.zero.xyz/host/via-router.floot.app/llms.txt)