_ registry / mcp http-sse · checked 3h ago

X1-BaaS

https://api.tazpal.com

Registry code: 6d85d434b6a3102b

api record

Use the `scrape` tool to fetch and extract web content as clean Markdown. The engine handles JavaScript rendering, anti-bot bypass, and DOM cleaning automatically. The `scrape` tool is paid. If the request carries no API key (`Authorization: Bearer baas_live_*`) or x402 payment proof, the engine returns a 402 with x402 payment requirements (Base USDC and/or Solana), which are relayed to you so you can pay and retry. Use `get_pricing` to check current pricing before scraping. Use `server_status` to check engine health and availability.

endpoint
https://api.tazpal.com/mcp
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 X1-BaaS live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is X1-BaaS free to use?
Yes — the hub reached it with no key and no payment.
What tools does X1-BaaS have?
3 tools: scrape, get_pricing, server_status.
Is X1-BaaS 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.2%

90 days 99.5%· all time 99.5%

latency
897ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 602 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
  • scrape a javascript-rendered page
  • convert a web page to markdown
  • check scrape pricing
takes → gives
web pages → text
tools
3 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. 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
1

distinct

settlements
5

last 2026-11-02

received on chain
0.025 USDC

counted from three payers (thin, concentrated)

_ what it can do 3 tools
2 open 1 never probed 2 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.

  • get_pricing reads open 3h ago

    Check current pricing and payment requirements for the BaaS scrape engine. Returns pricing info, supported networks, and payment instructions. No authentication required. Returns: Current pricing details and payment instructions.

    mcp-tool

    {
      "type": "object",
      "title": "get_pricingArguments",
      "properties": {}
    }
    arguments 5 lines
  • server_status reads open 3h ago

    Check the BaaS engine health and operational status. Returns browser status, uptime, x402 payment mode, and context count. Returns: Server health and diagnostic information.

    mcp-tool

    {
      "type": "object",
      "title": "server_statusArguments",
      "properties": {}
    }
    arguments 5 lines
  • scrape reads unknown 3h ago

    Scrape a URL and return content in your preferred format. Supported output formats: - markdown (default): Clean LLM-ready Markdown text - screenshot: PNG/JPEG image of the page - pdf: PDF document of the page - csv: Table data extracted as CSV - html: Sanitized HTML with scripts/ads removed This tool handles: - JavaScript rendering (SPA, dynamic content) - Anti-bot bypass (Cloudflare Turnstile, Datadome) - DOM cleaning (strips scripts, nav, footer, ads) - HTML-to-Markdown conversion (Mozilla Readability engine) - Automatic retry with escalating wait strategies - Domain cooldown to avoid rate-limiting - Response caching (5 min TTL) Args: url: The URL to scrape (must start with http:// or https://) output: Output format: "markdown" (default), "screenshot", "pdf", "csv", "html" wait_for_selector: Optional CSS selector to wait for before extraction (e.g., ".article-content") timeout_ms: Navigation timeout in milliseconds (default: 20000, max: 120000) block_media: Block images/fonts/video for faster loading (default: true) wait_strategy: Wait strategy: "default", "spa", "heavy", "cloudflare" (auto-detected if omitted) retry: Enable automatic retry on failure (default: true) bypass_cache: Skip cache, force fresh scrape (default: false) javascript: Custom JavaScript to execute after page load (e.g., "window.scrollTo(0, 1000)") Returns: Content in the requested format, or an error message.

    mcp-tool

    {
      "type": "object",
      "title": "scrapeArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url"
        },
        "retry": {
          "type": "boolean",
          "title": "Retry",
          "default": true
        },
        "output": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Output",
          "default": null
        },
        "javascript": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Javascript",
          "default": null
        },
        "timeout_ms": {
          "type": "integer",
          "title": "Timeout Ms",
          "default": 20000
        },
        "block_media": {
          "type": "boolean",
          "title": "Block Media",
          "default": true
        },
        "bypass_cache": {
          "type": "boolean",
          "title": "Bypass Cache",
          "default": false
        },
        "wait_strategy": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Wait Strategy",
          "default": null
        },
        "wait_for_selector": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Wait For Selector",
          "default": null
        }
      }
    }
    arguments 81 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.

_ 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 6d85d434b6a3102b.

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