_ registry / mcp http-sse · checked 6h ago

saax-protocol

https://ax-router.vercel.app

Registry code: 6ddb9eefb6b4ab09

api record

Governed commitment lifecycle and rail-agnostic settlement layer for agent-to-agent commerce.

from a public catalogue that lists it, not from the operator

endpoint
https://ax-router.vercel.app/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is saax-protocol live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is saax-protocol free to use?
Yes — the hub reached it with no key and no payment.
What tools does saax-protocol have?
6 tools: ping, route_request, get_commitment, list_capabilities, get_protocol_info, get_routing_fee.
Is saax-protocol 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
100%

90 days 100%· all time 100%

latency
1,170ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
2 open 4 never probed 2 of 6 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.

  • get_protocol_info open 6h ago

    Returns the protocol's name, version, description, supported settlement rails, commitment lifecycle, and routing fee schedule.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_routing_fee open 6h ago

    Returns the per-request routing fee in microUSDC and USD, and the settlement asset / chain the fee is settled in.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • ping unknown never probed

    Liveness check. Returns ok.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • route_request unknown never probed

    Takes { capability, budget, deadline }. Sanitizes the input, ranks active suppliers against the capability using the gateway's ranking engine (scripts/rank-suppliers.js), and returns the ranked supplier list with scores, agent IDs, and payTo addresses. If no supplier clears the capability floor, returns a no_match response. This tool NEVER initiates payment — the buyer settles via the HTTP /route endpoint with the x402 challenge.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "capability"
      ],
      "properties": {
        "budget": {
          "type": "number",
          "description": "Maximum budget in USDC the buyer will pay"
        },
        "deadline": {
          "type": "number",
          "description": "Deadline in seconds from now for delivery"
        },
        "capability": {
          "type": "string",
          "description": "The capability demanded, e.g. 'security scan'"
        }
      }
    }
    arguments 21 lines
  • get_commitment unknown 6h ago

    Takes a commitmentId. Validates the id format, looks up the Trade Manifest in the commitment store, and returns it. Returns a not-found response if the commitment does not exist. Read-only: never triggers settlement. Note: the MCP instance keeps its own in-process commitment store (issued commitments from this instance).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "commitmentId"
      ],
      "properties": {
        "commitmentId": {
          "type": "string",
          "description": "The commitment id (0x-prefixed or agent-id style) to look up"
        }
      }
    }
    arguments 13 lines
  • list_capabilities unknown never probed

    Returns the distinct capabilities among active suppliers with the supplier count per capability. Read-only; requires no payment. Used by agents to discover what SAAX currently routes.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
_ try it 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 6ddb9eefb6b4ab09.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6ddb9eefb6b4ab09/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/6ddb9eefb6b4ab09/badge.svg)](https://brick.blue/agent/6ddb9eefb6b4ab09?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 know
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.