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

tryx402-gateway

https://www.tryx402.app

Registry code: 412b4556f27b4c21

api record

Gateway that finds x402 endpoints and calls them for agents, paying from a card-funded USD wallet with spend tracking.

endpoint
https://www.tryx402.app/mcp
door code
302d1f3fff5caca6
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 tryx402-gateway live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is tryx402-gateway free to use?
Yes — the hub reached it with no key and no payment.
What tools does tryx402-gateway have?
10 tools: gateway_call, gateway_recharge, gateway_rebind, gateway_proxy_call, gateway_lookup, gateway_discover, gateway_plan, gateway_spent, ….
Is tryx402-gateway 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.1%· all time 99%

latency
979ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 958 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • discover x402 endpoints for a task
  • call paid x402 apis with a card-funded balance
  • top up a usd wallet balance
  • track agent spending
takes → gives
text, data → data, payments
tools
6 reads2 changes data2 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 10 tools
4 open 6 never probed 4 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.

  • gateway_plan reads open 4h ago

    Estimate a multi-call workflow before execution using live endpoint checks and the catalog as fallback.

    mcp-tool

    {
      "type": "object",
      "required": [
        "steps"
      ],
      "properties": {
        "steps": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "url": {
                "type": "string"
              },
              "body": {
                "type": "object"
              },
              "method": {
                "enum": [
                  "GET",
                  "POST",
                  "PUT",
                  "DELETE"
                ],
                "type": "string",
                "default": "POST"
              },
              "origin": {
                "type": "string"
              },
              "endpoint": {
                "type": "string"
              },
              "parameters": {
                "type": "object"
              }
            }
          },
          "description": "Ordered list of API steps"
        }
      }
    }
    arguments 42 lines
  • gateway_spent reads open 10h ago

    Retrieve active session spend metrics in USD, total spent, remaining budget and ledger breakdown. Free.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • gateway_check_balance reads open 10h ago

    Check wallet balance linked to this session (funded via Stripe recharge). Returns balance in USD.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • gateway_search reads open 4h ago

    Semantic discovery over the x402 tool catalogue. Query by intent (e.g. verified email, scraper).

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10
        },
        "query": {
          "type": "string",
          "description": "Intent or task description"
        }
      }
    }
    arguments 16 lines
  • gateway_call moves money unknown never probed

    Execute an authenticated HTTP request through the gateway with idempotency and request validation. Access requires an identified account with available entitlement.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Target HTTP 402 API endpoint URL"
        },
        "body": {
          "type": "object",
          "description": "JSON request payload"
        },
        "method": {
          "enum": [
            "GET",
            "POST",
            "PUT",
            "DELETE"
          ],
          "type": "string",
          "default": "POST"
        }
      }
    }
    arguments 26 lines
  • gateway_recharge changes data unknown never probed

    Generate a secure Stripe Checkout URL to top-up wallet balance in USD via card/Apple Pay.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "currency": {
          "type": "string",
          "default": "usd",
          "description": "Currency (usd)"
        },
        "amount_cents": {
          "type": "integer",
          "default": 1000,
          "description": "Amount in cents (e.g. 1000 = $10.00 USD)"
        },
        "customer_email": {
          "type": "string",
          "description": "Optional email for Stripe receipt"
        }
      }
    }
    arguments 19 lines
  • gateway_rebind changes data unknown never probed

    Re-bind this session to the wallet that PAID a Stripe checkout — the fix when gateway_lookup finds funds under the user email but calls are billed to an empty session wallet. Ask the user for the email used at checkout AND the Stripe checkout session id (cs_… on their receipt). Two-factor, zero friction: machine possession + receipt possession. One-shot per checkout, 48h window for cross-machine claims. On success this session switches to the paying wallet for all subsequent calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "checkout_session_id"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "The email address the user paid with at Stripe checkout"
        },
        "checkout_session_id": {
          "type": "string",
          "description": "Stripe checkout session id from the receipt (starts with cs_)"
        }
      }
    }
    arguments 17 lines
  • gateway_proxy_call moves money unknown never probed

    Call an x402 endpoint through the tryx402 FIAT PROXY — the no-crypto path paid from the hosted Stripe balance. Pricing is server-side (registry lookup); a 10% commission applies; budget check before debit; automatic refund on provider failure. Returns {status_code, headers, body, cost_cents, commission_cents, total_cents, new_balance_cents}.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Full URL to call (server resolves the price from its registry)"
        },
        "body": {
          "type": "object",
          "description": "JSON request body. Omit for GET requests."
        },
        "method": {
          "type": "string",
          "description": "HTTP method: GET or POST. Defaults to POST."
        }
      }
    }
    arguments 20 lines
  • gateway_lookup reads unknown 4h ago

    Recover wallet by email. Use when agent has lost context — ask the user their payment email to find their wallet.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Email used during Stripe checkout"
        }
      }
    }
    arguments 12 lines
  • gateway_discover reads unknown 10h ago

    Introspect an origin domain for available x402 endpoints, supported methods, and schemas.

    mcp-tool

    {
      "type": "object",
      "required": [
        "origin"
      ],
      "properties": {
        "origin": {
          "type": "string",
          "description": "Base URL of the provider (e.g. https://api.example.com)"
        }
      }
    }
    arguments 12 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 412b4556f27b4c21.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/412b4556f27b4c21/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/412b4556f27b4c21/badge.svg)](https://brick.blue/agent/412b4556f27b4c21?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
1
ok
0
failed
1
success rate
0%
median latency
121ms
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
—

1 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.