Get the list of Twitter/X accounts a user follows, paid per request in USDC on Base via x402.
What it does
The `/users/following` endpoint on twit.sh returns a paginated list of Twitter/X user profiles that a specific user follows, identified by their numeric user ID. It returns up to 50 profiles per page and supports 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. There are no API keys, OAuth flows, or accounts required. When an agent sends a request, the server responds with HTTP 402 and a machine-readable payment challenge. The agent settles $0.01 USDC on Base mainnet, retries with a payment proof header, and receives the data. The same `/users/following` path also supports POST (follow a user, $0.0075) and DELETE (unfollow a user, $0.005), both of which require the caller to supply Twitter session credentials (auth_token and ct0 cookies).
The data is sourced from publicly available profile and post information on the open web and shaped into clean JSON. The API covers users, tweets, lists, communities, articles, and authenticated actions (like, retweet, bookmark, follow, tweet creation/deletion). All endpoints settle payments in USDC on Base mainnet with no gas required from the caller.
Capabilities
Use cases
- —Building a social graph of a Twitter/X user's connections for analysis
- —Monitoring which accounts an influencer or brand follows over time
- —Populating agent knowledge bases with a user's follow list for recommendation or outreach
- —Automating follow/unfollow actions on Twitter/X via an AI agent
Fit
Best for
- —AI agents that need Twitter/X social graph data without API key setup
- —Autonomous workflows that can pay per request in USDC on Base
- —Developers wanting X v2-compatible JSON without an official X API subscription
Not for
- —Use cases requiring free or high-volume bulk data (pay-per-call adds up)
- —Applications needing private/protected account data (only public data is returned)
- —Callers without USDC on Base mainnet for payment
Quick start
# 1. First request returns 402 with payment challenge
curl 'https://x402.twit.sh/users/following?id=44196397'
# 2. Pay the USDC challenge, then retry with proof:
curl -H 'X-PAYMENT: <payment_proof>' \
'https://x402.twit.sh/users/following?id=44196397'Endpoint
Quality
Full OpenAPI schema with clear parameter definitions, pricing, and pagination details. The endpoint is live (402 challenge captured). However, response body schemas are not defined for the GET method, no example response JSON is available, and the /docs path returns 404.
Warnings
- —Response schema for GET /users/following is not documented — the 200 response only says 'Success' with no body definition.
- —Authenticated actions (POST follow, DELETE unfollow) require raw Twitter session cookies (auth_token, ct0) passed as query parameters, which is a security concern.
- —No example response body is provided in the OpenAPI spec or crawled pages.
Citations
- —GET /users/following returns up to 50 profiles per page with pagination support, priced at $0.01 USDChttps://x402.twit.sh
- —POST /users/following (follow) costs $0.0075 USDC and DELETE /users/following (unfollow) costs $0.005 USDChttps://x402.twit.sh
- —twit.sh uses x402 payment protocol — agents pay per request in USDC on Base mainnet with no API keys or accountshttps://x402.twit.sh
- —Data is sourced from publicly available profile and post information, shaped into X v2-compatible JSONhttps://x402.twit.sh