_ registry / mcp streamable-http

payapi-market

https://payapi.market

Registry code: 147f36de1d831d78

api record

PayAPI Market lists APIs an AI agent can call and pay for by itself, per request, in USDC on Base. No API key and no account are needed to call a listed API.

Use search_apis to find something by free text, list_apis to browse a category, and get_api to fetch one listing in full.

endpoint
https://payapi.market/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 3 tools

_ 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 3 tools
3 never probed 0 of 3 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.

  • search_apis unknown never probed

    Free-text search across the live catalogue. Matches listing name, description, category and provider name. Returns settlement-verified listings only unless verified_only is false. Free and read-only; spends nothing.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "What you are looking for, e.g. \"uk property\" or \"sanctions screening\"."
    },
    "verified_only": {
      "type": "boolean",
      "default": true,
      "description": "Restrict to settlement-verified listings. Default true."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • list_apis unknown never probed

    Browse the live catalogue, optionally filtered to one category. Omit category for everything. Returns settlement-verified listings only unless verified_only is false. Free and read-only; spends nothing.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 100,
      "minimum": 1
    },
    "category": {
      "type": "string",
      "description": "Exact category name. Call with no category first to see the valid values."
    },
    "verified_only": {
      "type": "boolean",
      "default": true
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • get_api unknown never probed

    Fetch a single live listing by its id or slug, including base_url, price range, network and verification state. Also returns a reliability object: score (0 to 100 or null), band (strong, established, thin, caution or unscored) and computed_at. Reliability is a running score from paid verifications, health history and payTo integrity, not a star rating and not a guarantee; unscored means it has not been computed for that listing yet. Method: https://payapi.market/how-an-agent-finds-payapi. Returns the listing whether or not it is verified, and reports payment_verified honestly. Free and read-only; spends nothing.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Listing uuid or slug, as returned by search_apis or list_apis."
    }
  },
  "additionalProperties": false
}
    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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/147f36de1d831d78/badge.svg)](https://brick.blue/agent/147f36de1d831d78)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
70%

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 payapi.market 2 entries

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.