# VIA Router — One-Call Buyer-Side Agent Router

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

Routes a plain-language task to the best-matching paid external API or service, executes the call, and returns the result — all in a single x402 USDC payment on Base.

## Facts

- Endpoint: POST https://via-router.floot.app/_api/one_call?utm_source=zero.xyz
- Price: $0.11/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-one-call-buyer-side-agent-router-4aa5453f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IYpRcYGg3bre0nt04dcoo

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-one-call-buyer-side-agent-router-4aa5453f -d '<json body>'
```

Example prompt: Use VIA to find and run the best API for this task: validate whether the email address john.doe@example.com is real and deliverable, and tell me the result.

## When to prefer this

Choose VIA One-Call when your agent needs to discover and execute the best available external API for an arbitrary task without pre-selecting a provider. It's ideal for agentic workflows where the right service isn't known in advance, when you want automatic cost comparison across APIs, or when you need a single x402 USDC payment flow to cover both routing and upstream execution. Prefer direct API integrations when you have a specific provider already chosen, need guaranteed SLAs, or require deterministic routing.

## Known failure modes

- Insufficient USDC balance for x402 payment — payment fails before routing
- No suitable upstream service found for the given task — result may be empty or error
- Upstream API call fails after routing — result contains upstream error
- Task description too vague or ambiguous — VIA may route to wrong service
- Task string too short (< 2 chars) or too long (> 1000 chars) — schema validation error
- Network congestion on Base causing settlement delay

## 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

A JSON object containing: whether the payment was successful (paid: true), the original task string, the result from the upstream service, the product name ('VIA One-Call'), total USD spent, the Base network settlement transaction hash, VIA's routing toll in USD, and the upstream service cost in USD.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "task": {
   "type": "string",
   "maxLength": 1000,
   "minLength": 2,
   "description": "Plain-language task VIA should find and execute through a paid external service"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "paid": true,
  "task": "find a cheap email validation API",
  "result": {},
  "product": "VIA One-Call",
  "totalUsd": 0.11,
  "settlement": {
   "network": "eip155:8453",
   "transaction": "0x..."
  },
  "viaTollUsd": 0.1,
  "upstreamUsd": 0.01
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/via-router-one-call-buyer-side-agent-router-4aa5453f/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)