Instagram profiles, posts, reels, comments, stories, hashtags and locations.
- Unified
Account,Post,Comment,Publication- Soon
- Direct
- 85 endpoints from 2 vendor APIs
- Live
Unified
Ask for Account, Post and Comment
SoonYou name the data; AIsa answers from TikHub or ScrapeCreators, 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.
Planned calls
A first draft. None of these is callable yet, and names and fields may change.
| Call | Returns | Sources behind it | From | Direct paths |
|---|---|---|---|---|
| Account2 calls | ||||
| Look up an account | Account | TikHub, ScrapeCreators | Soon | — |
| Followers of an account | Account[] | TikHub, ScrapeCreators | Soon | — |
| Post2 calls | ||||
| Recent posts from an account | Post[] | TikHub, ScrapeCreators | Soon | — |
| Search posts | Post[] | TikHub, ScrapeCreators | Soon | — |
| Comment1 call | ||||
| Comments under a post | Comment[] | TikHub, ScrapeCreators | Soon | — |
| Write1 call | ||||
| Publish a post | Publication | Your connected account | Soon | — |
Direct
Or call a vendor's endpoint yourself
LiveThe same Instagram 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.
TikHubfrom $0.001
tikhub70 endpoints70 of its 954 endpoints cover InstagramGET /apis/v1/tikhub/instagram/v1/fetch_location_infoReturns TikHub’s own JSONScrapeCreatorsfrom $0.0019scrape-creators15 endpoints15 of its 24 endpoints cover InstagramGET /apis/v1/instagram/basic-profileReturns ScrapeCreators’s own JSONEvery Instagram 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 |
|---|---|---|---|
| TikHub70 endpoints | |||
| GET | tikhub/instagram/v1/fetch_cities | instagram fetch_cities | from $0.001 |
| GET | tikhub/instagram/v1/fetch_explore_sections | instagram fetch_explore_sections | from $0.001 |
| GET | tikhub/instagram/v1/fetch_location_info | instagram fetch_location_info | from $0.001 |
| GET | tikhub/instagram/v1/fetch_locations | instagram fetch_locations | from $0.001 |
| GET | tikhub/instagram/v1/fetch_post_by_id | instagram fetch_post_by_id | from $0.001 |
| GET | tikhub/instagram/v1/fetch_post_by_url | instagram fetch_post_by_url | from $0.001 |
| GET | tikhub/instagram/v1/fetch_related_profiles | instagram fetch_related_profiles | from $0.001 |
| GET | tikhub/instagram/v1/fetch_search | instagram fetch_search | from $0.001 |
| ScrapeCreators15 endpoints | |||
| GET | instagram/basic-profile | basic-profile | from $0.0019 |
| GET | instagram/media/transcript | transcript | from $0.0019 |
| GET | instagram/post | post | from $0.0019 |
| GET | instagram/post/comments | comments | from $0.0019 |
| GET | instagram/profile | profile | from $0.0019 |
| GET | instagram/reels/search | search | from $0.0019 |
| GET | instagram/reels/trending | reels-trending | from $0.0019 |
| GET | instagram/search/hashtag | search-hashtag | from $0.0019 |
Which one to use
Unified
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.
Direct
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 Instagram comes back with the same fields as one on X, so a prompt written for one platform works on the next.
