_ registry / mcp + a2a streamable-http · checked 2h ago

via-router-discovery

https://via-router.floot.app

Registry code: 2a6b7b1a515c59ee

api record

Use free via_list_services and via_get_service, or via_api_compare for a paid comparison. With an x-credit-token connection header, each call costs0.01 USD of prepaid credit and requires a UUID requestId; reuse it only for retries of identical input. Without prepaid credit, use an authorized x402 buyer wallet for the0.01 USDC challenge. Never submit both payment methods. Credit loading: https://via-router.floot.app/credits. Use via_one_call_quote for a free toll quote, via_one_call for the existing buyer-approved x402 payment and delivery flow, and via_one_call_status for external Transit…

endpoint
https://via-router.floot.app/_api/mcp
door code
d66938751c304599
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
20 · newcomer
_ is it live, free and safe measured by this hub
Is via-router-discovery live?
Yes — it answered the hub's last check (checked 2h ago). It answered 97% of checks over the last 30 days.
Is via-router-discovery free to use?
Yes — the hub reached it with no key and no payment.
What tools does via-router-discovery have?
8 tools: via_get_service, via_one_call_quote, via_extract_web_lite, via_extract_page, via_api_compare, via_one_call_status, via_one_call, via_list_services.
Is via-router-discovery safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.1%

90 days 98.5%· all time 96.5%

latency
768ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 582 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 10 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
8

distinct

settlements
13

last 2026-11-06

received on chain
0.23 USDC

no flags

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • via_list_services open 2h ago

    Free VIA service discovery. Lists HTTP services and advertised prices; does not run research, charge, sign or purchase.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional topic or service-name filter"
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • via_get_service unknown 2h ago

    Free integration instructions for one VIA HTTP service: exact endpoint, JSON input schema, example and x402 payment steps. Does not execute the service or authorize payment.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Exact service name from via_list_services"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • via_one_call_quote unknown 2h ago

    Free quote for the VIA toll: VIA-owned delivery first, eligible paid supplier otherwise. Returns supplier cost, VIA margin and total. No wallet signature or payment. Continue only if ok and executionEnabled are true.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task",
        "maxUsdc"
      ],
      "properties": {
        "task": {
          "type": "string",
          "maxLength": 1000,
          "minLength": 2
        },
        "maxUsdc": {
          "type": "string",
          "pattern": "^(0|[1-9]\\d*)(\\.\\d{1,6})?$",
          "description": "Maximum approved total in USDC, including supplier and VIA margin."
        },
        "orderId": {
          "type": "string",
          "format": "uuid",
          "description": "Private client-generated UUIDv4. Required for execution; preserve it and the exact body for payment retry and recovery."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • via_extract_web_lite unknown never probed

    Web Text Lite: extract clean text, title and headings from a public HTML or plain-text page (up to 1 MiB, max 10000 characters; no PDF, OCR, JavaScript rendering or links) for 0.001 USDC on Base via x402. PDF URLs are refused before payment; use via_extract_page (0.02 USDC) for PDFs. Nothing is charged if extraction fails. Payment is only made after buyer approval.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "Public HTML or plain-text page; not a PDF"
        },
        "maxChars": {
          "type": "integer",
          "default": 10000,
          "maximum": 10000,
          "minimum": 500
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • via_extract_page unknown never probed

    Extract structured text from a public web page or PDF for 0.02 USDC on Base via x402. Payment is only made after buyer approval.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri"
        },
        "maxChars": {
          "type": "integer",
          "maximum": 100000,
          "minimum": 500
        },
        "includeLinks": {
          "type": "boolean"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • via_api_compare unknown never probed

    Compare APIs for a buyer task. Pay0.01 USDC on Base with an authorized x402 wallet, or0.01 USD of prepaid VIA credit if your MCP connection has an x-credit-token header. Prepaid calls require requestId: a fresh UUID per task, reused only to retry the same task without another debit. Returns a recommendation and alternatives. Supplier purchase is separate.

    mcp-tool

    {
      "type": "object",
      "required": [
        "intent"
      ],
      "properties": {
        "intent": {
          "type": "string",
          "maxLength": 500,
          "minLength": 2
        },
        "country": {
          "type": "string",
          "default": "US",
          "pattern": "^[A-Z]{2}$"
        },
        "language": {
          "enum": [
            "en",
            "pt"
          ],
          "type": "string",
          "default": "en"
        },
        "requestId": {
          "type": "string",
          "format": "uuid",
          "description": "Required for prepaid credit. New UUID per task; preserve it for retries of identical input."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • via_one_call_status unknown 17h ago

    Free status/recovery lookup for an external Transit order using its private UUIDv4. Never submits payment. Does not cover VIA-owned service receipts; 404 is not proof that a payment did not occur.

    mcp-tool

    {
      "type": "object",
      "required": [
        "orderId"
      ],
      "properties": {
        "orderId": {
          "type": "string",
          "format": "uuid",
          "description": "Private client-generated UUIDv4. Required for execution; preserve it and the exact body for payment retry and recovery."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • via_one_call unknown never probed

    Execute a VIA toll operation through the existing One-Call payment and delivery handler. First call without payment returns the live x402 offer; only after buyer approval, retry IDENTICAL task, maxUsdc and private orderId with the buyer-signed payload in params._meta['x402/payment']. Buyer pays VIA before an eligible external supplier is paid; VIA relays delivery and retains its margin. Only supported tasks/suppliers. No automatic signing or financial retry. Prepaid comparison credits do not fund this tool.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task",
        "maxUsdc",
        "orderId"
      ],
      "properties": {
        "task": {
          "type": "string",
          "maxLength": 1000,
          "minLength": 2
        },
        "maxUsdc": {
          "type": "string",
          "pattern": "^(0|[1-9]\\d*)(\\.\\d{1,6})?$",
          "description": "Maximum approved total in USDC, including supplier and VIA margin."
        },
        "orderId": {
          "type": "string",
          "format": "uuid",
          "description": "Private client-generated UUIDv4. Required for execution; preserve it and the exact body for payment retry and recovery."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2a6b7b1a515c59ee.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2a6b7b1a515c59ee/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2a6b7b1a515c59ee/badge.svg)](https://brick.blue/agent/2a6b7b1a515c59ee?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on floot.app 7 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.