77trust / 100

X Leads

by clinkagent.com in Company & people data

x402 APIPassing, checked 2 h ago

X/Twitter recruiter & lead finder for AI agents - search 'open to work', hiring posts, cofounder search, or any topic, and get the PEOPLE talking about it, enriched: bio, website, emails found in bios, follower count, location, DM-open flag, every matching post per person. Recruiting, cofounder search, B2B lead gen, influencer/community discovery. ?query=<advanced search>&max=20|40. Free masked sample: /x/leads/example. Raw tweets instead: /x/search $0.02. One person in depth: /x/person $0.15.

GET
https://clinkagent.com/x/leads
Price
$0.05
per call in USDC
Uptime
100%
last 30 days
Response time
306 ms
519 ms slowest 5%
Last check
Passed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://clinkagent.com/x/leads

Each call costs $0.05 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.

GET https://clinkagent.com/x/leads?max=20&query=%22open+to+work%22+web3+-filter%3Aretweets

Parameters

ParameterTypeRequiredDescription
maxstringNo One of: 20, 40.
querystringYes

Example response

The provider's example. We can't check it without paying.

{
  "lead_count": 8,
  "leads": [
    {
      "emails": [],
      "followers": 5000,
      "matched_posts": [],
      "username": "someone"
    }
  ],
  "result_count": 20
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://clinkagent.com/x/leads?max=20&query=%22open+to+work%22+web3+-filter%3Aretweets'

# 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 - 'https://clinkagent.com/x/leads?max=20&query=%22open+to+work%22+web3+-filter%3Aretweets' \
  | 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.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
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.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fclinkagent.com%2Fx%2Fleads
const res = await pay("https://clinkagent.com/x/leads?max=20&query=%22open+to+work%22+web3+-filter%3Aretweets");
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.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://clinkagent.com/x/leads?max=20&query=%22open+to+work%22+web3+-filter%3Aretweets")
    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
2 h agoPassed402641 ms$0.05
5 h agoPassed402288 ms$0.05
9 h agoPassed402295 ms$0.05
13 h agoPassed402276 ms$0.05
17 h agoPassed402281 ms$0.05
Show 10 older checks
20 h agoPassed402347 ms$0.05
23 h agoPassed402301 ms$0.05
26 h agoPassed402301 ms$0.05
29 h agoPassed402306 ms$0.05
32 h agoPassed402292 ms$0.05
35 h agoPassed402207 ms$0.05
40 h agoPassed402340 ms$0.05
45 h agoPassed402372 ms$0.05
2 days agoPassed402226 ms$0.05
2 days agoPassed402199 ms$0.05