_ registry / mcp streamable-http · checked 50m ago

botx402

https://api.botx402.io

Registry code: a7cb9b159c45280d

api record

botx402 sells one-shot reports, paid per run, to a human buyer. Call list_bots first to see which bots are available (the list can be empty). For a listed bot: call validate_<bot>_inputs with {"inputs": {...}} until it says the inputs are valid (free, nothing is charged; it lists every problem at once), then start_<bot> with the same JSON plus the buyer's "email". start_<bot> never charges anyone; it returns a Stripe checkout link that a person opens and pays. Show the user the link and ask them to pay; nothing runs until they do. Then call get_run with the receipt_id and access_token from…

endpoint
https://api.botx402.io/mcp
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
10 · newcomer
_ is it live, free and safe measured by this hub
Is botx402 live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is botx402 free to use?
Yes — the hub reached it with no key and no payment.
What tools does botx402 have?
2 tools: get_run, list_bots.
Is botx402 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 99.4%· all time 99.4%

latency
374ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 537 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • list paid analysis bots
  • validate inputs for an inventory reorder run
  • start a paid analysis run
  • fetch analysis run results
takes → gives
data → data
tools
2 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
9

distinct

settlements
53

last 2026-11-21

received on chain
0.53 USDC

concentrated

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

  • list_bots reads open 4h ago

    List the bots this server can run: what each one does, its price per run, what a run returns, its input schema, and the names of its validate_ and start_ tools. Free and read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_run reads unknown never probed

    Check a run started with a start_ tool and fetch its results. Needs the receipt_id AND the access_token that start_ returned: the token is the proof that the caller started the run, and without it nothing is returned. Status is awaiting_payment (the user has not paid yet), running, completed or failed. When completed, structuredContent.result is the bot's full JSON result, ready to act on, and pdf_url links the PDF report (presigned, expires after 7 days). Free and read-only; poll about once a minute.

    mcp-tool

    {
      "type": "object",
      "required": [
        "receipt_id",
        "access_token"
      ],
      "properties": {
        "receipt_id": {
          "type": "string",
          "description": "receipt_id from start_<bot>, like RG-202610-1A2B3C4D."
        },
        "access_token": {
          "type": "string",
          "description": "access_token from start_<bot>."
        }
      },
      "additionalProperties": false
    }
    arguments 18 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 a7cb9b159c45280d.

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