Get Twitter/X follower lists via pay-per-request x402 — $0.01 USDC on Base, no API key needed.
What it does
The `/users/followers` endpoint on twit.sh returns a paginated list of Twitter/X users who follow a specific account, identified by numeric user ID. It returns up to 50 follower profiles per page with cursor-based pagination via a `next_token` parameter. The response format is X v2 API-compatible JSON.
This endpoint is part of the broader twit.sh API, a payment-gated Twitter/X data service that uses the x402 protocol. Instead of API keys or OAuth, each request is paid individually in USDC on Base mainnet. When an unauthenticated agent hits the endpoint, it receives a 402 Payment Required response with a machine-readable payment challenge. The agent settles in USDC, retries with a payment proof header, and receives the data. The cost for this specific endpoint is $0.01 USDC per request.
The twit.sh API covers a wide range of Twitter/X data operations including user lookup (by username, ID, or search), tweet retrieval, search with advanced filters, community and list data, and authenticated actions like posting, liking, retweeting, and following. Data is sourced from publicly available profile and post information. The service requires no account creation and is designed for autonomous AI agents, with an npm CLI skill (`npx twitsh`) available for easy integration with Claude Code, Cursor, and other agent frameworks.
Capabilities
Use cases
- —Retrieving the follower list of a Twitter/X account for social graph analysis
- —Building audience overlap reports by comparing follower sets across accounts
- —Monitoring follower growth by periodically fetching follower pages
- —Feeding follower data into AI agent workflows without managing API keys
- —Identifying influencer audiences for outreach or research
Fit
Best for
- —AI agents that need Twitter follower data without OAuth setup
- —Developers who want pay-per-call pricing instead of monthly X API subscriptions
- —Autonomous workflows that can settle USDC payments on Base
- —Quick one-off follower lookups without account creation
Not for
- —High-volume bulk scraping of millions of followers (pagination at 50/page adds up)
- —Use cases requiring private/protected account follower data
- —Applications that cannot transact in USDC on Base mainnet
Quick start
curl -X GET "https://x402.twit.sh/users/followers?id=44196397" \
-H "X-PAYMENT: <x402_payment_proof>"Example
Request
{
"url": "https://x402.twit.sh/users/followers?id=44196397&next_token=abc123",
"method": "GET"
}Endpoint
Quality
Full OpenAPI schema with clear parameter definitions and pricing. The endpoint is live (402 challenge captured). However, no response schema or example response body is documented for this specific endpoint, and the /docs page returns 404. Pricing and pagination details are well-specified.
Warnings
- —No response schema defined for the 200 response — the shape of returned follower data is undocumented beyond being 'X v2 API-compatible JSON'.
- —The /docs endpoint returns 404; documentation is limited to the landing page and OpenAPI spec.
- —50 followers per page with $0.01/request means fetching all followers of a large account could become expensive.
Citations
- —The /users/followers endpoint costs $0.01 USDC per request and returns up to 50 follower profiles per pagehttps://x402.twit.sh
- —Payment is in USDC on Base mainnet via the x402 protocol with no account requiredhttps://x402.twit.sh
- —Data is sourced from publicly available profile and post information, shaped into X v2-compatible JSONhttps://x402.twit.sh
- —CLI skill available via npx twitsh, compatible with Claude Code, Cursor, and other agentshttps://x402.twit.sh