
One call returns an X account's follower counts grouped by tag category (Tier 1 VC, Ecosystems, Sectors). The answer shows how many of the account's followers carry each tag, organized by tag category.
1 live route on X, from $0.00 per call. Every route below answered our last live test on 2026-10-08; the gateway re-tests them daily.
The upstream price you are metered at, cheapest first. A route without a published price says so.
| Provider | Endpoint | Price |
|---|---|---|
Count an X account's smart followers by tag (a16z, Paradigm, Y Combinator...)GET get_tagged_followers_count | $0.00$0.0e+00 / 1k calls |
From a real call to the route: TwitterScore.
data[].tag_category_nameTag category (e.g. Tier 1 VC, Ecosystems)data[].tags[].tag_nameTag name (e.g. a16z, Ethereum)data[].tags[].tag_idTag ID for use in other endpointsdata[].tags[].cntCount of followers with this tagHTTP with your key in x-api-key, or the call_endpoint tool of our MCP server.
| Parameter | Type | Notes | |
|---|---|---|---|
| username | string · query | optional | X username without @ (or send twitter_id instead).e.g. VitalikButerin |
| twitter_id | string · query | optional | X numeric id (or send username instead). |
curl "https://fetchapi.co/api/gw/twitterscore/get_tagged_followers_count?username=VitalikButerin" \ -H "x-api-key: YOUR_KEY"
call_endpoint("twitterscore.get_tagged_followers_count", {"username": "VitalikButerin"}){
"data": [
{
"tags": [
{
"cnt": 136,
"tag_id": 1,
"tag_name": "a16z"
},
{
"cnt": 60,
"tag_id": 66,
"tag_name": "ConsenSys"
},
"… 1 more"
],
"tag_category_id": 1,
"tag_category_name": "Tier 1 VC"
},
{
"tags": [
{
"cnt": 29,
"tag_id": 36,
"tag_name": "CMS Holdings"
},
{
"cnt": 24,
"tag_id": 32,
"tag_name": "Fabric Ventures"
},
"… 1 more"
],
"tag_category_id": 2,
"tag_category_name": "Tier 2 VC"
},
"… 1 more"
],
"success": true
}Call it over HTTP or from any MCP client. Each key has a rate limit and a monthly cap; calls are metered at the upstream price.