_ registry / mcp + a2a streamable-http · checked 52m ago

peaje-peaje

https://usepeaje.com

Registry code: 7529132d40b94c85

api record

Peaje makes websites and APIs discoverable and readable by AI agents, letting owners optionally charge per request via protocols like x402, MCP, and MPP without requiring agents to use API keys. Use it when you want to check or improve how AI agents like ChatGPT, Claude, or Perplexity see your site. Call get_pricing first: it is free and lists every tool with its price. Each paid tool returns an HTTP 402 payment challenge (MPP) on the first call; pay it with a wallet that supports MPP or x402 and call again. There are no API keys and no accounts: the receipt comes back in the tool result.…

endpoint
https://usepeaje.com/mcp
door code
22d370b9dd06d550
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 peaje-peaje live?
Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
Is peaje-peaje free to use?
Yes — the hub reached it with no key and no payment.
What tools does peaje-peaje have?
2 tools: get_api_radar_by_dominio, get_pricing.
Is peaje-peaje 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
862ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 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_pricing open 52m ago

    List everything Peaje sells to agents and what each item costs. Free to call: use it before paying for anything else.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "detail": {
          "enum": [
            "summary",
            "full"
          ],
          "type": "string",
          "description": "summary: one line per item with its price (default). full: the complete pricing document with descriptions and how to pay."
        }
      }
    }
    arguments 14 lines
  • get_api_radar_by_dominio unknown 52m ago

    Agent-readiness score for any website, measured by Ora. Pass the domain (example.com) as dominio. Returns the score from 0 to 100, the grade, how far Peaje could raise it, and the top fixes with the points each one adds. A fresh scan can take up to a minute. · Free.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "dominio"
      ],
      "properties": {
        "query": {
          "type": "object",
          "description": "Optional query params for the endpoint",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {
            "type": "string"
          }
        },
        "dominio": {
          "type": "string",
          "description": "Path segment :dominio"
        }
      }
    }
    arguments 23 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 7529132d40b94c85.

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

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
1
failed
0
success rate
100%
median latency
875ms
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.

_ also on usepeaje.com 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.