_ registry / mcp http-sse · checked 15h 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 15h 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?
10 tools: ping, list_capabilities, get_evidence_verification, get_authority_validation, route_request, get_commitment, list_commitments, get_commitment_status, ….
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
243ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 5 checks · signed record
  • unknown → live
_ what it is for
topic
payments & commerce payment infrastructure
used for
  • route a request to a supplier by capability
  • get agent commerce routing fee
  • look up a commitment
  • list supplier capabilities
takes → gives
data → data
tools
5 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
2 open 8 never probed 2 of 10 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 reads open 15h ago

    Returns the SAAX Protocol version, available capability count, and the URL to the specification. Call this when an agent needs a one-time overview of the protocol. For pricing, use get_routing_fee. For the full capability list, use list_capabilities. For a liveness check, use ping.

    mcp-tool

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

    Returns the current routing fee schedule. Call this before initiating a routing request to determine the expected cost. For capability discovery, use list_capabilities. For protocol overview, use get_protocol_info.

    mcp-tool

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

    Returns a lightweight liveness response. Call this to verify the endpoint is reachable. Do not use for discovery, capability listing, or pricing — use get_protocol_info, list_capabilities, or get_routing_fee instead.

    mcp-tool

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

    Returns the capabilities currently indexed by the SAAX Router, with supplier counts per capability. Call this to discover what can be routed. For pricing of a specific capability, use get_routing_fee. For protocol overview, use get_protocol_info.

    mcp-tool

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

    Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "subscriptionEmail",
    "evidence",
    "commitment",
    "criterion"
  ],
  "properties": {
    "evidence": {
      "description": "The evidence object (evidenceId, evidenceType, issuer, subject, payload, payloadHash, signature, verificationScheme, commitmentId, acceptanceCriterionId, ...)"
    },
    "criterion": {
      "description": "The verification policy / acceptance criterion"
    },
    "commitment": {
      "description": "The commitment object the evidence binds to"
    },
    "subscriptionEmail": {
      "type": "string",
      "description": "The subscription email (must have an active SAAX Premium subscription)"
    }
  }
}
    arguments 25 lines
  • get_authority_validation unknown 2d ago

    Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "subscriptionEmail",
    "proof",
    "commitment"
  ],
  "properties": {
    "proof": {
      "description": "The AuthorityProof object (proofType, issuer, subject, scope, validFrom, validUntil, signature, verificationScheme, verificationMaterial)"
    },
    "commitment": {
      "description": "The commitment or requested action the proof must authorize"
    },
    "subscriptionEmail": {
      "type": "string",
      "description": "The subscription email (must have an active SAAX Premium subscription)"
    }
  }
}
    arguments 21 lines
  • route_request changes data unknown never probed

    Submits a capability request and returns ranked supplier matches. Commitment creation with payment runs through the HTTP POST /route endpoint, not this tool. Use list_capabilities first to discover available capabilities. For commitment lookup after routing, use get_commitment.

    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 reads unknown 15h ago

    Returns the full commitment object for a given commitment ID — including terms, state, manifest hash, and evidence references. Call this when an agent needs the complete commitment record. For status-only polling, use get_commitment_status. For listing all commitments for a subscriber, use list_commitments.

    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_commitments unknown never probed

    Returns all commitments associated with a subscription email. Requires an active SAAX Premium subscription. Call this to retrieve commitment history for a subscriber. For a single commitment by ID, use get_commitment. For status-only checks, use get_commitment_status.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "subscriptionEmail"
  ],
  "properties": {
    "subscriptionEmail": {
      "type": "string",
      "description": "The subscription email (must have an active SAAX Premium subscription)"
    }
  }
}
    arguments 13 lines
  • get_commitment_status unknown never probed

    Returns only the current lifecycle state for a given commitment ID, plus the recommended next action for the calling agent. Call this before retrying any commitment that timed out — an unknown outcome is a status check, not another POST. The next_action field tells the agent whether to retry, poll, or stop. For the full commitment record, use get_commitment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "commitmentId"
  ],
  "properties": {
    "commitmentId": {
      "type": "string",
      "description": "The commitment id to poll for its lifecycle state"
    }
  }
}
    arguments 13 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.