ToolVet
78trust / 100

Bot Score

by nostr.halowerk.com in Search & web

x402 APIPassing, checked 50 min ago

Fetches the recent notes of one public key across several relays and measures six independent signals: posting rate per day, the coefficient of variation of the intervals between posts, how many of those intervals sit within a few seconds of each other, the entropy of the hour-of-day distribution, the share of posts whose text repeats an earlier post verbatim, and the largest burst inside sixty seconds.

POST https://nostr.halowerk.com/bot-score

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
131 ms typical, 182 ms slowest 5%
Last check
50 min ago
Next check
any minute now

How to call it

POST https://nostr.halowerk.com/bot-score

Each call costs $0.004 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://nostr.halowerk.com/bot-score
content-type: application/json

{
  "pubkey": "beispiel"
}

Parameters

ParameterTypeRequiredDescription
daysintegerNoLength of the observation window in days. Default: 30.
kindsarray of integerNoEvent kinds to examine. Default is [1], plain text notes.
max_eventsintegerNoUpper bound on notes fetched per relay. Default: 300.
pubkeystringYesPublic key as 64 hex characters, npub or nprofile.
relaysarray of stringNowss relay addresses. Left empty, ten measured default relays are used.

Example response

The listing has no example response.

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.004.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://nostr.halowerk.com/bot-score' \
  -H 'content-type: application/json' \
  --data-raw '{"pubkey":"beispiel"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://nostr.halowerk.com/bot-score' \
  -H 'content-type: application/json' \
  --data-raw '{"pubkey":"beispiel"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.004 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.004" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.004 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fnostr.halowerk.com%2Fbot-score&method=POST
const res = await pay("https://nostr.halowerk.com/bot-score", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "pubkey": "beispiel"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.004 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.004"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://nostr.halowerk.com/bot-score",
        json={
            "pubkey": "beispiel",
        },
    )
    print(res.status_code, res.text)

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
50 min agoPassed402146 ms$0.004
5 h agoPassed402109 ms$0.004
9 h agoPassed402136 ms$0.004
13 h agoPassed402135 ms$0.004
16 h agoPassed402125 ms$0.004
20 h agoPassed402194 ms$0.004
24 h agoPassed402182 ms$0.004
27 h agoPassed402131 ms$0.004
31 h agoPassed402135 ms$0.004
35 h agoPassed402166 ms$0.004
38 h agoPassed402151 ms$0.004
42 h agoPassed402110 ms$0.004
45 h agoPassed402131 ms$0.004
2 days agoPassed402133 ms$0.004
2 days agoPassed402100 ms$0.004