X
Accounts, posts, comments, communities and lists from X, plus posting, liking and following through an account you connect.
- Unified
Account,Post,Comment,Publication· 39 calls- Soon
- Direct
- 61 endpoints from 3 vendor APIs
- Live
Ask for Account, Post and Comment
SoonYou name the data; AIsa answers from Twitter API or TikHub, whichever is fresh and working, and can switch between them without touching your code. Every value is tagged with its source, and you pay only when something comes back.
Start here
AccountReadLook up an accountTwitter API, TikHubfrom $0.001PostReadRecent posts from an accountTwitter API, TikHubfrom $0.001CommentReadReplies under a postTwitter API, TikHubfrom $0.001PostReadSearch postsTwitter API, TikHubfrom $0.001AccountReadFollowers of an accountTwitter API, TikHubfrom $0.001PublicationWritePublish a postAIsa X appMeteredEvery unified call on X
Billed only when something comes back. Writes go through AIsa’s own X app.
| Call | Returns | Sources behind it | From | Direct paths |
|---|---|---|---|---|
| Account10 calls · 16 direct paths behind them | ||||
| Look up an account | Account | Twitter API, TikHub | from $0.001 | 2 |
| Accounts by ID, in bulk | Account[] | Twitter API, TikHub | from $0.001 | 2 |
| An account’s about details | Account | Twitter API, TikHub | from $0.001 | 2 |
| Followers of an account | Account[] | Twitter API, TikHub | from $0.001 | 2 |
| Accounts it follows | Account[] | Twitter API, TikHub | from $0.001 | 2 |
| Show 5 more: verified followers, follow check, account search, affiliates, live status | ||||
| Post9 calls · 13 direct paths behind them | ||||
| Recent posts from an account | Post[] | Twitter API, TikHub | from $0.001 | 3 |
| Posts by ID | Post[] | Twitter API, TikHub | from $0.001 | 2 |
| Who reposted a post | Account[] | Twitter API, TikHub | from $0.001 | 2 |
| Quotes of a post | Post[] | Twitter API | Metered | 1 |
| Mentions of an account | Post[] | Twitter API | Metered | 1 |
| Show 4 more: thread context, articles, media, repost check | ||||
| Comment2 calls · 5 direct paths behind them | ||||
| Replies under a post | Comment[] | Twitter API, TikHub | from $0.001 | 4 |
| Replies written by an account | Comment[] | TikHub | from $0.001 | 1 |
| Community & list8 calls · 15 direct paths behind them | ||||
| Community details | Community | Twitter API, TikHub | from $0.001 | 2 |
| Posts in a community | Post[] | Twitter API, TikHub | from $0.001 | 3 |
| Community members | Account[] | Twitter API, TikHub | from $0.001 | 2 |
| Posts on a list | Post[] | Twitter API, TikHub | from $0.001 | 2 |
| Show 4 more: list members, list followers, moderators, community search | ||||
| Search & trends2 calls · 4 direct paths behind them | ||||
| Search posts | Post[] | Twitter API, TikHub | from $0.001 | 2 |
| Trending topics | Trend[] | Twitter API, TikHub | from $0.001 | 2 |
| Write8 calls · 8 direct paths behind them | ||||
| Publish a post | Publication | AIsa X app | Metered | 1 |
| Delete a post | — | AIsa X app | Metered | 1 |
| Like a post | — | AIsa X app | Metered | 1 |
| Follow an account | — | AIsa X app | Metered | 1 |
| Show 4 more: unlike, unfollow, upload media, connect an account | ||||
Or call a vendor's endpoint yourself
LiveThe same X data through each vendor's own paths and fields, on your AIsa key. You pick the vendor, and your code is written against its format, so switching later means rewriting the call.
twitter28 endpointsprofiles, posts, communities, lists, trendsGET /apis/v1/twitter/user/infoReturns the vendor’s own user objectTikHubfrom $0.001tikhub25 endpoints25 of its 954 endpoints cover XGET /apis/v1/tikhub/twitter/web/fetch_user_profileReturns TikHub’s own JSONAIsa X actionsfrom $0.000001aisa-twitter8 endpointspost, delete, like, follow, upload mediaGET /apis/v1/twitter/post_twitterReturns X’s own post objectEvery X endpoint
Read live from api.aisa.one. Metered prices start at the amount shown and vary with the request. A path opens its page in the docs.
| Method | Path | Name | Price |
|---|---|---|---|
| Twitter API28 endpoints | |||
| GET | twitter/list/tweets_timeline | Get List Tweet TimeLine | from $0.0015 |
| GET | twitter/tweet/replies/v2 | Get Tweet Replies V2 | from $0.011 |
| GET | twitter/user/last_tweets | Get User Tweets | from $0.003 |
| GET | twitter/user/mentions | Get User Mentions | from $0.003 |
| GET | twitter/user/tweet_timeline | Get User TimeLine | from $0.0057 |
| GET | twitter/user/followers | List User Followers | from $0.0033 |
| GET | twitter/user/followings | List User Followings | from $0.0036 |
| GET | twitter/user/batch_info_by_ids | Batch Get User Info By UserIds | from $0.00018 |
| TikHub25 endpoints | |||
| GET | tikhub/twitter/web/fetch_check_follow | twitter fetch_check_follow | from $0.001 |
| GET | tikhub/twitter/web/fetch_check_retweet | twitter fetch_check_retweet | from $0.001 |
| GET | tikhub/twitter/web/fetch_community_info | twitter fetch_community_info | from $0.001 |
| GET | tikhub/twitter/web/fetch_community_members | twitter fetch_community_members | from $0.001 |
| GET | tikhub/twitter/web/fetch_community_timeline | twitter fetch_community_timeline | from $0.001 |
| GET | tikhub/twitter/web/fetch_latest_post_comments | twitter fetch_latest_post_comments | from $0.001 |
| GET | tikhub/twitter/web/fetch_list_followers | twitter fetch_list_followers | from $0.001 |
| GET | tikhub/twitter/web/fetch_list_members | twitter fetch_list_members | from $0.001 |
| AIsa X actions8 endpoints | |||
| GET | twitter/auth_twitter | OAuth_Twitter | $0.000001 |
| GET | twitter/delete_twitter | Delete Tweet | from $0.01 |
| GET | twitter/follow_twitter | Follow User | from $0.015 |
| GET | twitter/like_twitter | Like Tweet | from $0.015 |
| GET | twitter/post_twitter | Post Twitter | from $0.015 |
| GET | twitter/unfollow_twitter | Unfollow User | from $0.01 |
| GET | twitter/unlike_twitter | Unlike Tweet | from $0.01 |
| GET | twitter/upload_media | Upload Media | $0.000001 |
Which one to use
When you want fields that stay the same across vendors and platforms, a fallback when one source fails, and to pay only when something comes back.
When you need a parameter or field only one vendor has, or you've already built on that vendor's format.
The same Account and Post everywhere
An account on TikTok comes back with the same fields as one on X, so a prompt written for one platform works on the next.