The transparency. Their full OpenAPI spec is public, so I could see exactly how each endpoint bills before spending anything. I verified it myself with their balance endpoint: follower-list pages bill exactly 1 unit per call, and a deprecated endpoint that returned HTTP 410 billed nothing at all. A full scan of a ~1,060-follower account took 43 requests in about 3 minutes, and the results cross-checked 89 out of 90 against a reference list I had collected directly (the one difference was a genuinely new follower). Response payloads are clean JSON with everything I need in one call, including profile images, so I am not chaining extra requests. Support on Telegram answered a detailed billing question within a day. Review collected by and hosted on G2.com.

The pricing structure punishes small starts. Until you have deposited $100 in total you pay roughly 20 times the headline per-request rate, which makes early evaluation feel disproportionately expensive, and card top-ups lose 15 percent to processing fees deducted from your balance rather than added on top (only crypto avoids that). The docs also do not surface that two endpoint families returning identical follower data differ about 2x in cost per user returned, so you can silently overpay unless you read the spec carefully and measure it yourself. Legacy endpoints also get deprecated as Instagram changes upstream, so older tutorials go stale quickly. A minor annoyance: their Cloudflare setup rejects Python's default urllib user agent, which cost me time before I switched clients. Review collected by and hosted on G2.com.