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

PayAI x402 Facilitator

https://facilitator.payai.network

Registry code: 71e6c1f7bf28b4c2

api record

This server exposes the PayAI x402 facilitator for checking supported payment kinds, verifying signed payments, settling them, and browsing Bazaar discovery data. settle_payment broadcasts a real on-chain transaction and moves funds; it is idempotent per signed payload, so resubmitting an identical payload returns its recorded outcome. GET-backed tools are free and unauthenticated.

endpoint
https://facilitator.payai.network/mcp
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
0 · newcomer
_ is it live, free and safe measured by this hub
Is PayAI x402 Facilitator live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is PayAI x402 Facilitator free to use?
Yes — the hub reached it with no key and no payment.
What tools does PayAI x402 Facilitator have?
5 tools: verify_payment, settle_payment, get_discovery_stats, get_supported, list_discovery_resources.
Is PayAI x402 Facilitator 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
99.3%

90 days 99.5%· all time 99.5%

latency
490ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 395 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce payment infrastructure
used for
  • verify an x402 payment
  • settle an x402 payment on-chain
  • list supported payment networks
  • browse x402 payable resources
takes → gives
data → data
tools
4 reads1 moves money
_ 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 5 tools
3 open 2 never probed 3 of 5 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_discovery_stats reads open 2h ago

    Returns aggregate statistics for the PayAI Bazaar catalog and its settlement activity. Use it for a compact view of catalog size and payment volume rather than individual resources.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_supported reads open 2h ago

    Returns the payment networks, schemes, assets, and facilitator addresses currently supported by PayAI. Use it before constructing payment requirements when you need live capability data.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • list_discovery_resources reads open 2h ago

    Lists x402-payable resources published in the PayAI Bazaar catalog. Use limit and offset to page through APIs, MCP tools, and agent services available for discovery.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • verify_payment reads unknown never probed

    Verifies a signed x402 payment payload against the supplied payment requirements. It checks validity but moves no funds.

    mcp-tool

    {
  "type": "object",
  "required": [
    "paymentPayload",
    "paymentRequirements"
  ],
  "properties": {
    "x402Version": {
      "enum": [
        1,
        2
      ],
      "type": "integer"
    },
    "paymentPayload": {
      "type": "object"
    },
    "serverExtensions": {
      "type": "object"
    },
    "paymentRequirements": {
      "type": "object"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • settle_payment moves money unknown never probed

    Broadcasts the payment on-chain and moves real funds; it is idempotent per signed payload, so resubmitting the identical payload returns the recorded outcome. Treat errorReason "settlement_pending" as unresolved and call again with the identical arguments to poll.

    mcp-tool

    {
  "type": "object",
  "required": [
    "paymentPayload",
    "paymentRequirements"
  ],
  "properties": {
    "x402Version": {
      "enum": [
        1,
        2
      ],
      "type": "integer"
    },
    "paymentPayload": {
      "type": "object"
    },
    "serverExtensions": {
      "type": "object"
    },
    "paymentRequirements": {
      "type": "object"
    }
  },
  "additionalProperties": false
}
    arguments 26 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 71e6c1f7bf28b4c2.

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

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 payai.network 1 entry

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.