Sourcelane

X (Twitter) Followers Contact Extractor

X (Twitter)

Operated by Sourcelane✓ verified

Scans an X (Twitter) account's followers and/or following lists to extract contact information and profile metadata for lead generation and outreach. The connector parses profile bios to detect and return email addresses, website URLs (resolving shortened links), and social links (Instagram, LinkedIn, YouTube, TikTok, GitHub, Telegram, Linktree, and more), and records which bio keywords matched. It supports relationship selection (followers/following/both), filtering by presence of contact info, bio keywords, location keywords, follower-count threshold, and verification status, and emits per-profile contact records containing contact details plus profile metadata such as username, display name, bio text, location, follower/following/tweet counts, verification flag, account creation date, DM availability, profile image, profile URL, and a resume cursor for scanning very large audiences. Operates without login or cookies.

Verified Sep 28, 12:10 AM

$0.004

per contact

Up to 100 per call. Only pay for results returned; failed calls are refunded.

What people use it for

Trust & reliability

7d uptime trend
WindowUptimeSuccess ratep50p95Calls
24h————0
7d————0
30d————0

Calling contract

Call it through Sourcelane's gateway or MCP server. We run the connector, apply your agent's spend guardrails, and bill only the results returned.

Call it via Sourcelane

curl -X POST https://cool-puffin-608.convex.site/v1/call \
  -H "Authorization: Bearer sl_live_your_agent_key" \
  -H "Content-Type: application/json" \
  -d '{"listing":"x-followers-contact-extractor","params":{"bioKeywords":[],"maxItems":5},"maxResults":10}'

Request params

FieldTypeRequiredDescription
modestringoptionalScan the account's followers, the accounts it follows, or both.
maxItemsintegeroptionalStop after this many profiles with contact info have been found. Set 0 for no limit (bounded by Max Profiles to Scan). Capped at 100 per call.
maxScanintegeroptionalUpper bound on how many follower/following profiles are examined looking for contact info. Set 0 to scan the whole list.
requireEmailbooleanoptionalReturn only profiles that expose an email address in their bio.
requireWebsitebooleanoptionalReturn only profiles with a non-social website link (bio link or profile URL).
bioKeywordsarrayoptionalKeep only profiles whose bio contains at least one of these words or phrases (case-insensitive). Leave empty to skip this filter.
locationKeywordsarrayoptionalKeep only profiles whose location field contains one of these words (e.g. "London", "NY", "Australia"). Leave empty to skip this filter.
minFollowersintegeroptionalSkip profiles with fewer followers than this. 0 disables the filter.
onlyVerifiedbooleanoptionalKeep only blue-verified profiles.
resolveShortLinksbooleanoptionalFollow t.co redirects so website links come back as real URLs (e.g. https://example.com) instead of https://t.co/abc. Slightly slower.
pageIdstringoptionalPaste NEXT_PAGE_ID from the previous run's Key-value store to continue scanning where it left off. Only valid for Followers or Following mode, not Both.

Each result contains

FieldTypeDescription
scrapedFromUsernamestringScraped From Username
relationshipstringRelationship
usernamestringUsername
userIdstringUser Id
namestringName
biostringBio
locationstringLocation
emailsarrayEmails
websitesarrayWebsites
socialLinksarraySocial Links
matchedKeywordsarrayMatched Keywords
isVerifiedbooleanIs Verified
followersCountinteger—
followingCountinteger—
tweetsCountinteger—
createdAtstring—
canDmboolean—
profilePicturestring—
profileUrlstring—

Use X (Twitter) Followers Contact Extractor from Claude, ChatGPT or Cursor

Pick your tool and connect in under a minute. Then just ask — for example: “Find the 50 most-liked tweets about 'MCP servers' this month and summarise the takes.”

Connect Claude

Web, desktop and mobile. Paste one URL.

  1. 1Copy your personal connector URL
  2. 2In Claude open Settings → Connectors → Add custom connector
  3. 3Paste the URL and click Add — done
Manual setup (config files, REST, Python) +

Claude Code

Adds the Sourcelane MCP server with your key as a header.

terminal
claude mcp add --transport http sourcelane https://cool-puffin-608.convex.site/mcp \
  --header "Authorization: Bearer sl_live_your_agent_key"

Claude Desktop (config file)

Alternative to the connector URL: add to claude_desktop_config.json, then restart Claude.

claude_desktop_config.json
{
  "mcpServers": {
    "sourcelane": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://cool-puffin-608.convex.site/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer sl_live_your_agent_key"
      }
    }
  }
}

Cursor & Windsurf

Add to ~/.cursor/mcp.json (or Windsurf's mcp_config.json).

mcp.json
{
  "mcpServers": {
    "sourcelane": {
      "url": "https://cool-puffin-608.convex.site/mcp",
      "headers": {
        "Authorization": "Bearer sl_live_your_agent_key"
      }
    }
  }
}

VS Code

Save as .vscode/mcp.json. VS Code prompts for your key once.

.vscode/mcp.json
{
  "servers": {
    "sourcelane": {
      "type": "http",
      "url": "https://cool-puffin-608.convex.site/mcp",
      "headers": {
        "Authorization": "Bearer ${input:sourcelane-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "sourcelane-key",
      "description": "Sourcelane agent key",
      "password": true
    }
  ]
}

ChatGPT Custom GPT (Actions)

Create a GPT → Actions → Import from URL, then Authentication: API Key, Bearer.

OpenAPI schema URL
https://sourcelane-amber.vercel.app/openapi.json

REST

One POST. Pass maxResults to cap cost.

curl
curl -X POST https://cool-puffin-608.convex.site/v1/call \
  -H "Authorization: Bearer sl_live_your_agent_key" \
  -H "Content-Type: application/json" \
  -d '{"listing":"x-followers-contact-extractor","params":{"bioKeywords":[],"maxItems":5},"maxResults":10}'

Python, LangChain, CrewAI, OpenAI Agents SDK…

Wrap the REST call as a tool, or point an MCP client at the endpoint.

python
import requests

res = requests.post(
    "https://cool-puffin-608.convex.site/v1/call",
    headers={"Authorization": "Bearer sl_live_your_agent_key"},
    json={
        "listing": "x-followers-contact-extractor",
        "params": {"bioKeywords":[],"maxItems":5},
        "maxResults": 10,
    },
    timeout=300,
)
body = res.json()
print(body["receipt"]["chargedMicros"], "micro-USD for", body["receipt"]["results"], "results")
print(body["data"])

Reviews

—

0 reviews

5
0
4
0
3
0
2
0
1
0

Leave a review

Loading reviews…