Instagram Follower Growth Benchmarking for Competitor Accounts

A single follower count is a snapshot, not a signal. Knowing a competitor sits at 84,000 followers today tells you almost nothing about whether they're growing, stalled, or losing people faster than they're gaining them. What actually matters is the same number pulled on a schedule, across the same set of accounts, so this week's count has something to sit next to.

That's a different job than checking one profile by hand. It means picking a competitor set, pulling all of them the same way on a fixed cadence, and storing each run so growth rate — not just headcount — becomes something you can actually compare.

If you're an agent (or building one) reading this rather than a human, the full machine-readable schema for every endpoint below lives at mindcase.co/skills.md.

What does a follower count alone miss?

Three things a single pull can't tell you:

• Direction. 84,000 followers says nothing about whether that number was 80,000 a month ago or 88,000. The count only becomes useful next to an earlier count from the same account.
• Relative pace. A brand gaining 500 followers a week looks fine in isolation and mediocre next to a competitor gaining 2,000 in the same window. Benchmarking only works across accounts pulled the same way, on the same day.
• What's driving it. Instagram Profiles API also returns posts (total post count) and lastPostDate alongside followers — so a growth spike that lines up with a burst of new posts reads differently than one with no posting-cadence change at all.

How do you pull follower counts for a list of competitor accounts?

usernames on Instagram Profiles API takes an array, so a whole competitor set comes back in one call rather than one request per account.

curl -X POST "https://api.mindcase.co/v1/data/instagram/profiles/run?wait=true" \
-H "Authorization: Bearer $MINDCASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "params": {
    "usernames": ["glossier", "fentybeauty", "rarebeauty"]
  }
}'

# $0.002 per profile — 3 profiles = $0.006

Each row comes back with followers, following, posts, verified, businessAccount, and lastPostDate among its 25 fields. Run the same call on a schedule — daily is tight enough to catch a launch-driven spike, weekly is enough for slower-moving categories — and store each run with its timestamp. The endpoint itself has no history or "since" parameter: it returns current state only, so tracking change over time is entirely a matter of storing your own snapshots and diffing them, the same way you'd diff any other point-in-time API response.

How do you turn snapshots into a growth rate?

Once two or more snapshots exist for the same username, the comparison is arithmetic, not a new API call:

growth_rate = (followers_today - followers_last_snapshot) / followers_last_snapshot

Run that per account, per period, and rank the competitor set by growth rate instead of raw follower count — a smaller account gaining 8% a month is outpacing a larger one gaining 1%, even though its absolute numbers are still behind.

What can't you get this way?

Two cases.

You don't get a reason for the change. The endpoint reports the number, not why it moved — a spike could be a product launch, a viral post, a purchased-followers campaign, or Instagram cleaning up bot accounts across the platform. posts and lastPostDate give a posting- cadence signal to correlate against, but confirming the actual cause still means checking Instagram Posts & Reels API for what a competitor published around the same window.

There's no push notification. Nothing alerts you when a competitor's follower count crosses a threshold — benchmarking stays pull-based, on whatever cadence you schedule it.

Which endpoint should you use for which job?

FAQ