JP

Twitter Account Info

Collect public profile details, audience metrics, and verification signals for one or more Twitter accounts

原文 · en-US訳文に戻す

開発者
料金
$0.0015 / 件から
最終更新
2026-09-18

概要

Twitter and X profile pages mix identity, audience size, verification, and protection signals in a layout that is hard to compare across accounts. This app turns those public profiles into a consistent record set so research, partnership, and monitoring teams can work from the same identifiers, metrics, and timestamps.

The value is the joined profile snapshot: displayed name, username, account ID, public URL, follower and following figures, verification and protection flags, bio text, and collection time stay together for each submitted username. That makes it easier to qualify creators, compare audience scale, and keep a watch list current without reconstructing profiles by hand.

Data notes

The data comes from the public Twitter profile associated with each submitted username. One record is produced for each submitted username when the source returns a profile or a no-data marker. Duplicate submitted usernames are removed across collected pages. Audience counts, bio text, professional attributes, location, and timestamps retain the source text; a source value can be unavailable and appear empty. Follower count, Following count, Fast followers, Like count, Listed count, Media count, and Post count are kept as source text rather than normalized numbers. Can DM, Media tag, Protected account, Translator, Custom timelines, Graduated access, and Sensitive are also retained as source text, even when they look like yes/no flags. Has email, Verified, and YouTube linked are true/false values. Collected at and Joined at are preserved as supplied, without inferring a timezone. Private, suspended, and login-only accounts are outside the coverage.

What the results look like

Each record represents the public profile collected for one submitted Twitter username.

Account nameUsernameFollower countVerifiedSubmitted accountNo data
💫Etoiles💫000uTSIDER2No000uTSIDERNo
demo.accountYes

Additional values include Avatar URL, Profile URL, Account ID, Bio, Affiliate label, Business ID, Can DM, Media tag, Cover photo URL, Collected at, Entity type, Fast followers, Following count, Custom timelines, Graduated access, Profile entities, Has email, Protected account, Translator, YouTube linked, Joined at, Source keyword, Like count, Listed count, Location, Media count, Pinned tweets, Sensitive, Professional info, Interstitial type, Post count, and Translator type.

Use cases

  • Qualify partnership targets by comparing Account name, Username, and Follower count across a watch list.
  • Map public presence by lining up Profile URL, Bio, Location, and Joined at for accounts you already monitor.
  • Separate empty outcomes from usable profiles by checking No data together with Submitted account before using Like count or Post count.
  • Distinguish public versus restricted profiles by reading Protected account, Verified, and Sensitive together with Account name.

適用範囲と境界

Each run accepts 1 to 200 Twitter usernames and returns at most one public profile record per username when data is available.

  • 適している用途
  • When you need a current public profile snapshot for specific Twitter accounts
  • When you need displayed audience size, verification, protection, and public profile signals in one record
  • 適さない用途
  • When you need posts, comments, or search results rather than account-level profile information
  • When you do not have a Twitter username to collect

失敗時の処理

開発者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。

  1. 1If no profile data is returned, verify the username and confirm the account is still public
  2. 2Retry later after rate limiting, temporary unavailability, or a timeout
  3. 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
  4. 4If authentication fails, verify the API Key configured for the execution environment

入力

この App の呼び出しに必要なパラメータで、manifest.json の input.schema から生成されています。

  • Twitter username listitems必須array<object>
    The Twitter usernames to collect. Submit 1 to 200 items; each item needs one username.
    件数最大 200 件例[{"account":"000uTSIDER"}]

出力

1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。

  • Submitted accounttask_itemstring
    The username submitted for this record
    例000uTSIDER
  • No datano_databoolean
    Whether this submitted username returned no public profile
    例false
  • Source keywordkeywordstring
    The source keyword associated with the collected account
    例000uTSIDER
  • Account IDaccount_idstring
    The Twitter account identifier returned for the profile
    例1652063959627841537

サンプルデータ

output.schema から生成したサンプルです。サンプル値のないフィールドには構造上のプレースホルダーを使用しています。

output.example
{
  "task_item": "000uTSIDER",
  "no_data": false,
  "keyword": "000uTSIDER",
  "account_id": "1652063959627841537",
  "account_name": "💫Etoiles💫",
  "account_avatar_url": "https://pbs.twimg.com/profile_images/1718476282885808128/3IcN2Gim_normal.jpg",
  "account_home_url": "https://x.com/000uTSIDER",
  "account_signature": "she/her",
  "affiliates_highlighted_label": "{\"label\":null}",
  "biz_id": "000uTSIDER",
  "can_dm": "false",
  "can_media_tag": "true",
  "cover_photo_url": "<cover_photo_url>",
  "crawl_time": "2026-08-27T14:07:55",
  "entity_type": "user",
  "fans_count": "2",
  "fast_followers_count": "0",
  "friends_count": "17",
  "has_custom_timelines": "false",
  "has_graduated_access": "true",
  "info": "{\"description\":{\"hashtags\":null,\"urls\":null,\"userMentions\":null},\"url\":null}",
  "is_mail": false,
  "is_protected": "false",
  "is_translator": "false",
  "is_verified": false,
  "is_youtube": false,
  "joined_date": "2023-04-29T05:35:28",
  "likes_count": "7093",
  "listed_count": "0",
  "location": "<location>",
  "media_count": "5",
  "pinned_tweet_ids": "<pinned_tweet_ids>",
  "possibly_sensitive": "false",
  "professional": "<professional>",
  "profile_interstitial_type": "<profile_interstitial_type>",
  "publish_content_count": "202",
  "translator_type_enum": "none",
  "user_handle": "000uTSIDER"
}

連携方法

この App は MCP、API、SDK、ファイルエクスポートのいずれでも連携でき、どのチャネルも同じ能力と料金を共有します。すべてのリクエストは Authorization: Bearer ヘッダーで認証し、認証情報には API Key(長期有効。Data Hub コンソールで作成)を使用します。MCP クライアントは OAuth によるキー不要のログインにも対応しています。CLI や Skill など、さらに多くの連携方法も準備中です。 この App は非同期で実行され、途中でキャンセルできます:キャンセル後、実行は停止します。納品済みのレコードは保持され、課金対象になります。

MCP(Model Context Protocol)を使うと、Claude や Cursor などの AI クライアントからこの App を直接呼び出せます。クライアントと認証方式を選び、下の設定をコピーしてください。

クライアント設定

Bearer の後の値を長期有効な API Key に置き換えてください。あらゆるクライアント、CI、ヘッドレス環境で利用できます。

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=hello_moto/twitter-account-info",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

AI に設定を任せる

設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します(デフォルトではログインを案内し、API Key をチャットに送るよう求めることはありません)。

detail.access.mcp.composeHint

料金

Task start

返される件数にかかわらず、実行の送信 1 回ごとに課金されます。

$0.0001/ 回
Returned profile

正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。

$0.0015/ 件

複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。

Credits を確認

今すぐ試す

パラメータを入力して実行してください。結果は実際の呼び出しによるものです。

サンプル
パラメータは送信前に input.schema で検証されます
$0.0015 / 件から