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

AgentPay APIs

https://agentpay.agentpay-apis.workers.dev

Registry code: 6230ee0f9818aa5b

api record

Paid tools. Pay per call with x402 (USDC on Algorand or Base) via params._meta["x402/payment"], or add header "Authorization: Bearer <api key>" to the MCP client config (free trial key: https://agentpay.agentpay-apis.workers.dev/credits/trial; buy credits: https://agentpay.agentpay-apis.workers.dev/credits/buy). Listing tools is free.

endpoint
https://agentpay.agentpay-apis.workers.dev/mcp
door code
daa80272212d48fd
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 AgentPay APIs live?
Yes — it answered the hub's last check (checked 5h ago). It answered 99% of checks over the last 30 days.
Is AgentPay APIs free to use?
Yes — the hub reached it with no key and no payment.
What tools does AgentPay APIs have?
8 tools: tools_pdf_text, tools_sitemap, tools_feed, lookup_dns, lookup_domain_report, lookup_ip, extract_page, lookup_whois.
Is AgentPay APIs 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
98.5%

90 days 98.9%· all time 99.1%

latency
572ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 372 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
search & web scraping & fetch
used for
  • extract a page as markdown
  • look up dns records
  • get a domain report
  • parse an rss feed
  • extract pdf text
takes → gives
web pages, text → data, text
tools
8 reads
_ 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 also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
5

distinct

settlements
18

last 2026-10-30

received on chain
0.095 USDC

concentrated, shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 8 tools
8 never probed 0 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.

  • tools_pdf_text reads unknown 23h ago

    Extract per-page text from a PDF URL (up to 20MB). Costs $0.01 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "URL of a PDF"
    }
  }
}
    arguments 12 lines
  • tools_sitemap reads unknown 23h ago

    List a site's URLs from its sitemaps (follows robots.txt and sitemap indexes). Costs $0.005 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Site origin or sitemap URL"
    },
    "limit": {
      "type": "integer",
      "description": "Max URLs (default 5000)"
    }
  }
}
    arguments 16 lines
  • tools_feed reads unknown 5h ago

    Parse an RSS, Atom or JSON Feed into normalized JSON items. Costs $0.005 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Feed URL"
    },
    "limit": {
      "type": "integer",
      "description": "Max items (default 50)"
    }
  }
}
    arguments 16 lines
  • lookup_dns reads unknown 23h ago

    Resolve DNS records (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, PTR, SRV). Costs $0.005 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Hostname to resolve"
    },
    "type": {
      "type": "string",
      "description": "Record type, default A"
    }
  }
}
    arguments 16 lines
  • lookup_domain_report reads unknown 14h ago

    One-call domain report: registration, DNS, email provider, SPF/DMARC, hosting. Costs $0.02 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain name"
    }
  }
}
    arguments 12 lines
  • lookup_ip reads unknown 14h ago

    IP network owner, range, country and reverse DNS. Costs $0.01 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "IPv4 or IPv6 address"
    }
  }
}
    arguments 12 lines
  • extract_page reads unknown 5h ago

    Fetch a URL and return markdown, metadata and links. Costs $0.005 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "http(s) URL to read"
    },
    "maxChars": {
      "type": "integer",
      "description": "Max markdown characters (1000-200000, default 50000)"
    }
  }
}
    arguments 16 lines
  • lookup_whois reads unknown 5h ago

    Domain registration data (registrar, created/expires, status, nameservers) via RDAP. Costs $0.01 USDC per call (x402 or credits).

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain name"
    }
  }
}
    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 6230ee0f9818aa5b.

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