Follower Graph
by nostr.halowerk.com in Company & people data
Fetches kind 3 contact lists over up to twelve relays. Because kind 3 is replaceable, several relays regularly hold different versions; only the one with the highest created_at is used and the answer states which relays carried that version and how many older versions were seen, so a stale relay never quietly overwrites a current list. At depth 1 the answer is the account and its outgoing follows.
POST https://nostr.halowerk.com/follower-graph
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 136 ms typical, 184 ms slowest 5%
- Last check
- 39 min ago
- Next check
- any minute now
How to call it
POST https://nostr.halowerk.com/follower-graph
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/follower-graph
content-type: application/json
{
"pubkey": "beispiel"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
depth | integer | No | 1 returns the account and its follows. 2 also fetches the contact lists of its contacts. One of: 1, 2. Default: 1. |
max_contacts | integer | No | Upper bound on contacts reported for the root account. Default: 200. |
pubkey | string | Yes | Public key as 64 hex characters, npub or nprofile. |
relays | array of string | No | wss relay addresses. Left empty, ten measured default relays are used. |
second_degree_sample | integer | No | How many contact lists to fetch at depth 2. Higher values cost time, not money. Default: 15. |
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/follower-graph' \
-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/follower-graph' \
-H 'content-type: application/json' \
--data-raw '{"pubkey":"beispiel"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Ffollower-graph&method=POST
const res = await pay("https://nostr.halowerk.com/follower-graph", {
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/follower-graph",
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 39 min ago | Passed | 402 | 136 ms | $0.004 |
| 5 h ago | Passed | 402 | 116 ms | $0.004 |
| 9 h ago | Passed | 402 | 133 ms | $0.004 |
| 13 h ago | Passed | 402 | 146 ms | $0.004 |
| 16 h ago | Passed | 402 | 138 ms | $0.004 |
| 20 h ago | Passed | 402 | 139 ms | $0.004 |
| 24 h ago | Passed | 402 | 144 ms | $0.004 |
| 27 h ago | Passed | 402 | 184 ms | $0.004 |
| 31 h ago | Passed | 402 | 41 ms | $0.004 |
| 35 h ago | Passed | 402 | 43 ms | $0.004 |
| 38 h ago | Passed | 402 | 136 ms | $0.004 |
| 42 h ago | Passed | 402 | 134 ms | $0.004 |
| 45 h ago | Passed | 402 | 156 ms | $0.004 |
| 2 days ago | Passed | 402 | 143 ms | $0.004 |
| 2 days ago | Passed | 402 | 128 ms | $0.004 |