X Twitter Profile Lookup avatar

X Twitter Profile Lookup

Pricing

from $4.50 / 1,000 results

Go to Apify Store
X Twitter Profile Lookup

X Twitter Profile Lookup

Bulk Twitter profile lookup exports up to 1,000 identity-matched public X profiles per run with 38 possible sparse fields and $0.00250 per result.

Pricing

from $4.50 / 1,000 results

Rating

5.0

(2)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

2

Bookmarked

132

Total users

2

Monthly active users

10 days ago

Last modified

Share

X Twitter Profile Lookup is a bulk twitter profile lookup that converts 1–1,000 known public X handles or profile URLs into sparse 38-field account records. It supports repeatable audience research, creator qualification, monitored account panels, and enrichment workflows that need identity-matched rows rather than copied pages.

Apify Users Apify Runs $0.00250 / result 38-field profiles API + MCP ready

  • One run accepts a required list of 1–1,000 strict handles, @handles, or canonical HTTPS profile URLs.
  • Each retained row has a matching requested/returned username and up to 38 sparse top-level fields.
  • Unavailable or identity-mismatched accounts produce no placeholder row and no Result charge.
  • Avatar and banner fields remain only when their images can be stored successfully.

The smallest useful FREE-tier run costs $0.01 for Actor Start plus $0.00250 for one saved Profile Result, or $0.01250 total.

Why Choose X Twitter Profile Lookup

Known-account batching. Submit one account for a low-risk test or up to 1,000 identifiers in one run. Case-insensitive deduplication preserves first-seen order and prevents duplicate work.

Profile depth. A successful row can cover identity, public bio and location, verification labels, account dates, follower and content counts, professional category, public links, pinned-post details, posting-source labels, stored imagery, and processing provenance.

Honest partial outcomes. One missing account does not erase valid profiles from the same batch. Optional timeline failure does not discard the core profile, while a wrong returned identity is rejected.

Sparse data. Missing values remain absent rather than becoming guessed facts. Consumers can distinguish an observed zero or false value from a field the source did not provide.

Quick Start Guide

Step 1: Configure

Open the input form and keep OpenAI, or replace it with another known 1–15 character X handle. @OpenAI and https://x.com/OpenAI normalize to the same identity.

Step 2: Run

Start the Actor and wait for the terminal ready, unavailable, and failed counts. A valid-looking handle can still be unavailable, so inspect the Dataset count separately.

Step 3: Collect

Export successful rows as JSON, CSV, Excel, XML, or RSS. Preserve user_id, user_name, processed_at, and the run ID when joining or comparing observations.

{"usernames":["OpenAI"]}

Input Parameters

X Twitter Profile Lookup exposes one required input property.

ParameterTypeRequiredLimitsDescription
usernamesarray of stringsYes1–1,000X handles, @handles, or exact HTTPS X/Twitter one-segment profile URLs

Handles use letters, digits, and underscores and contain 1–15 characters. URLs must use https, an exact X/Twitter host, no credentials or custom port, and one profile path segment. Post, search, list, and embedded foreign URLs are rejected. Duplicate normalized handles are removed.

The Actor does not accept display-name searches, keywords, IDs, cookies, credentials, follower limits, location filters, or date filters. Invalid items are ignored only when at least one usable handle remains.

Output Data Schema

Each retained Dataset item is one identity-matched public profile with up to 38 top-level fields.

GroupFieldsMeaning
Identityuser_id, user_name, display_name, description, locationPublic account identity and self-presented context
Verificationverified, blue_verified, verified_type, verified_at, affiliate_labelSource-reported labels and dates, not independent verification
Countsfollowers_count, following_count, statuses_count, favourites_count, listed_count, media_countCurrent public counter snapshots
Accountcreated_at, protected, sensitive, account_type, account_category, creator_subscriptions, business_affiliates, highlighted_tweetsSource-reported account flags and category fields
Links and mediaprofile_urls, description_urls, avatar_url, banner_urlPublic links plus successfully stored imagery
Timelinepinned_tweet, pinned_tweet_ids, posting_sourcesAvailable pinned-post observation and first-seen source labels
Otherbirthdate, profile_language, custom_timelines, default_profileSparse public source fields
Processingstatus, processor, processed_atOutcome, producing Actor, and observation time

This JSON is abbreviated; a real row can expose up to 38 top-level keys.

{
"user_id":"4398626122",
"user_name":"OpenAI",
"display_name":"OpenAI",
"description":"OpenAI’s mission is to ensure AGI benefits all of humanity.",
"followers_count":5102563,
"blue_verified":true,
"status":"success",
"processor":"https://apify.com/agentx/x-twitter-profile-lookup",
"processed_at":"2026-08-12T18:55:00+00:00"
}

Optional keys are omitted when unavailable. posting_sources is a first-seen sample from the recent public timeline, not a complete device history. pinned_tweet is omitted when no pinned entry is returned.

Integration Examples

Use Actor ID PVpATK5xrZz1JBNvn or name agentx/x-twitter-profile-lookup through HTTP, SDKs, automation platforms, or MCP.

$curl -X POST "https://api.apify.com/v2/acts/PVpATK5xrZz1JBNvn/runs?token=$APIFY_TOKEN" -H "Content-Type: application/json" -d '{"usernames":["OpenAI"]}'
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("PVpATK5xrZz1JBNvn").call(run_input={"usernames": ["OpenAI"]})
items = list(client.dataset(run["defaultDatasetId"]).iterate_items())
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('PVpATK5xrZz1JBNvn').call({ usernames: ['OpenAI'] });
const { items } = await client.dataset(run.defaultDatasetId).listItems();

For MCP, connect the Apify MCP server, select agentx/x-twitter-profile-lookup, and pass {"usernames":["OpenAI"]}. Poll an existing run ID when a client wait expires rather than launching a duplicate.

Pricing

X Twitter Profile Lookup costs $0.00250 per saved Profile Result on FREE, plus $0.01 Actor Start; the smallest successful run is $0.01250.

EventFREEBRONZESILVERGOLDPLATINUMDIAMOND
Actor Start$0.01000$0.01000$0.01000$0.01000$0.01000$0.01000
Profile Result$0.00250$0.00225$0.00200$0.00188$0.00188$0.00188

Actor Start is once per run. Profile Result repeats only for saved rows. One FREE result costs $0.01 + $0.00250 = $0.01250; 100 results cost $0.01 + (100 × $0.00250) = $0.26. Unavailable users have no Result charge. Prices can change; check the pricing page.

Use Cases

Creator qualification. Compare bio, location, labels, counts, links, and pinned context before a human reviews a known account.

Audience panels. Schedule selected handles and retain processed_at to observe directional changes in counts, descriptions, categories, or pinned posts.

CRM enrichment. Add a public X identity and timestamped profile fields to a record that already has a known handle. Do not infer consent or private contact data.

Account monitoring. Detect unavailable accounts, changed handles, or sparse responses while keeping identity validation and human review in the workflow.

Research exports. Build reproducible account tables for public-interest, brand, developer, media, or market research without presenting a snapshot as verified truth.

Alternatives

Manual profile review is preferable for one consequential account when current posts and page context matter. It is hard to repeat consistently across a larger known list and copied data loses provenance.

X offers official User Lookup endpoints for approved developers with authentication. Use them when the official API, its quotas, fields, and policy contract are required. This Actor is independent and is not the official X API.

Choose a search or post product when you need discovery by name/keyword, timelines, replies, followers, following lists, email discovery, private data, or engagement analytics.

Limits and Troubleshooting

  • Fewer rows than inputs: invalid and duplicate handles are normalized away; unavailable or identity-mismatched users produce no placeholder.
  • No row: verify the 1–15 character handle, open the public profile, inspect terminal counts, and retry later.
  • Missing field: absence means “not retained from this snapshot,” not factual zero.
  • Missing avatar/banner: the text record survives when an image cannot be validated and stored.
  • No pinned post: pinned_tweet is optional and depends on the recent public timeline response.
  • Changing counts: preserve processed_at and compare repeated observations before interpretation.

Open an Issue with the run ID, redacted input, terminal message, Dataset count, observed keys, and expected behavior. Never send tokens or private data.

Trust and Reliability

Apify provides isolated runs, storage, schedules, webhooks, Dataset exports, and API access. The Actor declares one 1–1,000-item input and a 38-field sparse output contract.

The requested normalized handle must equal the returned source handle. Core profile success survives optional pinned-timeline failure, but a wrong identity is rejected. Result billing occurs only after successful persistence.

X's official username lookup reference documents the same 1–15 character handle pattern and identifies public fields such as name, description, location, links, protection, metrics, verification, imagery, and pinned-post ID.

Public visibility does not remove privacy, intellectual-property, database-right, contractual, employment, advertising, or consumer-protection obligations. Establish a lawful purpose, minimize retention, protect tokens and Datasets, and honor deletion or suppression duties.

Do not use the output for harassment, sensitive profiling, spam, access-control evasion, or high-impact automated decisions without appropriate authority and human review. A follower, label, or posting source does not imply consent, authenticity, affiliation, or endorsement.

Review the current X Terms of Service and Apify General Terms before production use.

Frequently Asked Questions

How do I perform a bulk twitter profile lookup without an X developer key?

Submit known public handles to the Actor with an Apify token. It does not request an X developer key, but it remains independent from the official X API.

Can I use full X profile URLs?

Yes. Exact HTTPS one-segment profile URLs normalize to the same case-insensitive handle as plain and @handle forms.

Does the Actor search by display name?

No. It resolves known handles only and does not discover accounts by names, bios, or keywords.

Is there a free Twitter profile API?

This Actor is pay per event. The current smallest successful FREE-tier run costs $0.01250 rather than promising permanently free access.

Can I schedule runs to monitor X profiles over time?

Yes. Retain processed_at and compare snapshots cautiously because public values and availability can change.

Does posting_sources identify every device?

No. It contains first-seen public posting-source labels from the recent timeline response and is not a complete device history.

AgentX includes 77 Actors across social, jobs, property, shopping, vehicle, media, and automation categories. The three closest extensions are:

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask about handles, sparse profile fields, unavailable accounts, pricing, Datasets, or integrations in the AgentX community on Telegram; for a reproducible bug, open an Issue with the run ID and exact redacted input.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 12, 2026