# Wallet to Twitter & Farcaster Lookup (`starl3xx/wallet-to-twitter-farcaster-lookup`) Actor

Resolve Ethereum and EVM wallet addresses to the X (Twitter) handles and Farcaster accounts their owners published onchain. Attested, never guessed, with the class of evidence labelled on every row. Bulk CSV input, eight chains, and a reverse mode that returns the wallets behind a handle.

- **URL**: https://apify.com/starl3xx/wallet-to-twitter-farcaster-lookup.md
- **Developed by:** [starl3xx](https://apify.com/starl3xx) (community)
- **Categories:** Lead generation, Social media, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Wallet to Twitter and Farcaster lookup

Turn a list of Ethereum or EVM **wallet addresses** into the **X (Twitter) handles** and **Farcaster accounts** their owners published, and run it in reverse to find every wallet attested to a handle. Backed by a 4.85 million wallet identity index across eight onchain networks.

This Actor returns only identities a wallet owner published themselves. It does not guess, and when it has nothing it says so.

### Why this is different from scraping posts

Most wallet-to-Twitter tools search X for posts that **contain** an address and ask a language model who the owner probably is. That is the wrong way round. The commonest reason an address appears in a public post is that it belongs to somebody else: a scam call-out, a drainer warning, a dust-sender complaint, a block explorer link someone pasted.

This Actor reads the opposite direction. Every match comes from something the owner did:

- a Farcaster verification, signed by the account holder
- an onchain record the wallet owner wrote, such as an ENS `com.twitter` text record
- an attested social sign-in
- a manually verified record

Each row is labelled with which class of evidence it came from, so you can set your own confidence bar instead of trusting a score somebody else assigned. Over 99.9% of the X handles in the index arrive by one of the first two routes.

### Handles that no longer reach anybody

Having an account and reaching a person are different claims, and most tools conflate them.

Of 473,215 distinct X handles resolved against X itself: **70.1% are live, 20.1% are suspended, and 9.8% were never claimed**. Close to a third of the handles on a typical holder list reach nobody at all. Where the check has been run, each row carries an `x_reachability` value of `live`, `suspended`, `unclaimed` or `reassigned`, so you can drop the dead ones before you spend anything on reach.

An empty `x_reachability` means the handle was not checked. It never means nobody is behind it.

### How to use it

1. Get a free API key at [walletlink.social](https://walletlink.social). The free allowance is 100 matches every 30 days.
2. Choose a lookup mode: wallets to social accounts, or a handle back to its wallets.
3. Paste your addresses, or a whole CSV column. Anything shaped like an EVM address is picked out.
4. Run it, then export the dataset as CSV, JSON or Excel.

### Input

| Field | What it does |
| --- | --- |
| `lookupMode` | `wallets`, `x_handle` or `farcaster_username` |
| `walletAddresses` | EVM addresses, one per row |
| `walletText` | Paste a CSV column or a newline-separated list instead |
| `handle` | The handle to reverse, for the two reverse modes |
| `apiKey` | Your walletlink.social key, starting with `wts_live_` |
| `includeMisses` | Keep a row per address submitted so the output lines up with your input |
| `maxReversePages` | Reverse pages to fetch, 100 wallets each |

### Output

One flat row per wallet, ready for a spreadsheet:

```json
{
  "wallet": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
  "found": true,
  "x_handle": "VitalikButerin",
  "x_url": "https://x.com/VitalikButerin",
  "x_verified": true,
  "x_reachability": "live",
  "farcaster_username": "vitalik.eth",
  "farcaster_url": "https://farcaster.xyz/vitalik.eth",
  "farcaster_followers": 123456,
  "farcaster_fid": 5650,
  "ens_name": "vitalik.eth",
  "evidence": "onchain, farcaster",
  "last_updated": "2026-09-14T00:00:00.000Z",
  "stale": false
}
```

Fields are flat on purpose, because these datasets are exported to CSV far more often than they are read as JSON.

### What it costs

The Actor itself is free to run. It calls the walletlink.social API with your key, and that API is metered in **matches**, where one match is one wallet resolved to an X handle or a Farcaster account.

A wallet that resolves to nothing costs nothing, which on most lists is the majority of them. The free allowance is 100 matches every 30 days. Credit packs start at $29 for 250 matches and last 12 months, with no subscription.

Reverse lookups are the expensive direction: one page returns up to 100 wallets and bills one match per wallet returned, so a single page can spend an entire free allowance. `maxReversePages` defaults to 1 for that reason.

### Coverage

Eight onchain networks: Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, HyperEVM and Robinhood Chain.

Match rates depend far more on which chain a list comes from than on anything else about it. Measured across 26 real collections: Base 46.2% of holders reachable, Ethereum 16.6%. Plan against the chain your holders are actually on.

### Frequently asked questions

**Does it find an account for every wallet?** No, and no honest tool does. Most wallets never published a social identity. You are told which resolved and which did not.

**Is this scraped from X?** No. Nothing here is read from a post, a display name or a bio.

**Can I look up a handle instead?** Yes. Set `lookupMode` to `x_handle` or `farcaster_username` to get the wallets attested to it.

**What if someone asked to be removed?** Suppressed wallets and handles are filtered at read time and return the same shape as a wallet that was never indexed.

**Is there an API or an MCP server?** Both. See [walletlink.social/mcp](https://walletlink.social/mcp) and [docs.walletlink.social](https://docs.walletlink.social).

# Actor input Schema

## `lookupMode` (type: `string`):

Forward: wallets in, social accounts out. Reverse: one handle in, the wallets attested to it out.

## `walletAddresses` (type: `array`):

EVM addresses, one per row. Used when the mode is 'Wallet addresses to social accounts'.

## `walletText` (type: `string`):

Paste a CSV column or a newline-separated list. Anything that looks like an EVM address is picked out, so a whole CSV row works. Merged with the list above.

## `handle` (type: `string`):

The X handle or Farcaster username, used when the mode is one of the reverse options. A leading @ is fine.

## `apiKey` (type: `string`):

Starts with wts\_live\_. Create one free at https://walletlink.social — the free allowance is 100 matches every 30 days, and wallets that resolve to nothing never count against it.

## `includeMisses` (type: `boolean`):

Keep a row for every address submitted, so the output lines up with your input list. Turn off to keep only the matches.

## `maxReversePages` (type: `integer`):

Each page returns up to 100 wallets and costs one match credit per wallet returned, so one page can spend an entire free allowance. Raise this deliberately.

## Actor input object example

```json
{
  "lookupMode": "wallets",
  "walletAddresses": [
    "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
    "0xfd22004806a6846ea67ad883356be810f0428793",
    "0x983110309620d911731ac0932219af06091b6744"
  ],
  "includeMisses": true,
  "maxReversePages": 1
}
```

# Actor output Schema

## `results` (type: `string`):

Every wallet submitted, matched or not, so the output lines up with the list you put in.

## `reachable` (type: `string`):

Only the wallets that resolved to an X handle or a Farcaster account.

## `csv` (type: `string`):

The same rows as CSV, ready for a campaign tool.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "walletAddresses": [
        "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
        "0xfd22004806a6846ea67ad883356be810f0428793",
        "0x983110309620d911731ac0932219af06091b6744"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("starl3xx/wallet-to-twitter-farcaster-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "walletAddresses": [
        "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
        "0xfd22004806a6846ea67ad883356be810f0428793",
        "0x983110309620d911731ac0932219af06091b6744",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("starl3xx/wallet-to-twitter-farcaster-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "walletAddresses": [
    "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
    "0xfd22004806a6846ea67ad883356be810f0428793",
    "0x983110309620d911731ac0932219af06091b6744"
  ]
}' |
apify call starl3xx/wallet-to-twitter-farcaster-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starl3xx/wallet-to-twitter-farcaster-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HgTVcgujAuktP3GYj/builds/I8oBEa7iUVtg3aDxF/openapi.json