_ registry / mcp + a2a http-sse · checked 4h ago

apistead-marketplace

https://apistead.qd.je

Registry code: 40553de56de57fb3

api record
endpoint
https://apistead.qd.je/mcp
door code
706d071f79bf0669
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 apistead-marketplace live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is apistead-marketplace free to use?
Yes — the hub reached it with no key and no payment.
What tools does apistead-marketplace have?
8 tools: get_api, get_routes, get_receipt, check_reliability, submit_listing, list_bundles, list_apis, search_apis.
Is apistead-marketplace 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
100ms

last good check

priced tools
0

of 8 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, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 16 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
30

last 2026-11-12

received on chain
0.373 USDC

counted from three payers (thin, concentrated)

_ what it can do 8 tools
3 open 5 never probed 3 of 8 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.

  • list_bundles open 4h ago

    List prepackaged API workflows with a route sequence, cost estimate and a ready-to-use agent prompt. Use a bundle when the user asks for an outcome rather than a single endpoint.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "category": {
          "type": "string",
          "description": "Optional bundle category filter."
        }
      }
    }
    arguments 10 lines
  • list_apis open 4h ago

    Browse the live catalogue with optional category and network filters. Use search_apis when you know what you need; use list_apis to explore.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Page size, default 20."
        },
        "cursor": {
          "type": "string",
          "description": "Opaque cursor from a previous response."
        },
        "network": {
          "enum": [
            "base"
          ],
          "type": "string",
          "description": "Network filter. APIStead is Base only."
        },
        "category": {
          "type": "string",
          "description": "Category filter."
        }
      }
    }
    arguments 27 lines
  • search_apis open 4h ago

    Search agent-ready APIs by capability, category, network and price. Use this first when you need a data source or tool. Discovery is free and never returns a payment challenge.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum results, default 20."
        },
        "query": {
          "type": "string",
          "description": "Free-text search, e.g. 'US ZIP' or 'sanctions'."
        },
        "network": {
          "enum": [
            "base"
          ],
          "type": "string",
          "description": "Network filter. APIStead is Base only."
        },
        "category": {
          "type": "string",
          "description": "Optional category filter, e.g. 'Compliance'."
        },
        "max_price": {
          "type": "number",
          "description": "Maximum price per call in USDC, e.g. 0.01.",
          "exclusiveMinimum": 0
        },
        "verified_only": {
          "type": "boolean",
          "description": "Only return listings with a paid verification receipt."
        }
      }
    }
    arguments 36 lines
  • get_api unknown never probed

    Fetch one listing by slug or id. Returns the provider, routes, prices, networks, verification state, reliability and agent links. Read this before paying.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id_or_slug"
      ],
      "properties": {
        "id_or_slug": {
          "type": "string",
          "description": "Listing slug or id, e.g. 'us-zip-code-api'."
        }
      }
    }
    arguments 13 lines
  • get_routes unknown never probed

    Return every route on one listing with method, path, price, example request and example response. Use this to construct a valid paid call.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id_or_slug"
      ],
      "properties": {
        "id_or_slug": {
          "type": "string",
          "description": "Listing slug or id."
        }
      }
    }
    arguments 13 lines
  • get_receipt unknown never probed

    Return the paid canary verification record for a listing, including network, last verified date and receipt URL. A null receipt means the listing is not settlement-verified.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id_or_slug"
      ],
      "properties": {
        "id_or_slug": {
          "type": "string",
          "description": "Listing slug or id."
        }
      }
    }
    arguments 13 lines
  • check_reliability unknown never probed

    Return the reliability score, band, 30-day uptime and last check time. Use it before routing a live agent to a provider.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id_or_slug"
      ],
      "properties": {
        "id_or_slug": {
          "type": "string",
          "description": "Listing slug or id."
        }
      }
    }
    arguments 13 lines
  • submit_listing unknown never probed

    APIStead Marketplace is not accepting new listing submissions yet. This tool returns the current status.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 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 40553de56de57fb3.

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