How was this list compiled?

Scraped GitHub `/network/dependents` for `subzeroid/instagrapi` (2,964 repositories total at time of writing), enriched each with star count and metadata via the GitHub GraphQL API, then sorted by stars. The refresh script lives at `scripts/fetch-dependents.py` in this site's source tree. Snapshot: 2026-05-02.

Why is the list capped at the top tier?

Below roughly five stars the list is mostly personal forks and one-evening scripts. The 20+ star band is where you find substantial single-developer projects worth linking, and the 100+ band is where projects start showing real community uptake.

Are these projects actively maintained?

Star count is a popularity proxy, not a maintenance signal. Some entries below are explicitly marked archived; for the rest, check the last commit date and open-issue volume before depending on the code. The list reflects who built things on `instagrapi`, not who is currently shipping.

Does this include private/closed-source projects?

No. `/network/dependents` only surfaces public repositories that declare `instagrapi` in a manifest GitHub can parse (`requirements.txt`, `pyproject.toml`, `setup.py`, `Pipfile`). Teams running `instagrapi` inside private services do not appear here.

Can I add my project?

If your repo is public and lists `instagrapi` in its dependency manifest, you already qualify — the list rebuilds from `/network/dependents` on each refresh. The same is true for `aiograpi` users; they share a separate dependents page captured here.

Projects using instagrapi: 25 standout tools from 1,300+ public repos

Picking a library is partly a question of “who else is using it.” This page answers that for instagrapi with real numbers: 2,964 public GitHub repositories list instagrapi in their dependency manifest, of which 1,322 are still alive enough for the GitHub API to return metadata. Below is a curated cut from that long tail — top community projects by stars, grouped by what they actually do — plus the official subzeroid ecosystem the maintainer team runs around the library itself.

The instagrapi family

These four projects are maintained by the same team that ships instagrapi. Together they cover the full stack: synchronous and asynchronous Python clients, a REST wrapper for non-Python callers, an interactive OSINT REPL, and a downloader CLI.

Project	Stars	What it is
subzeroid/instagrapi	6 130	The library itself — synchronous Python client for Instagram’s private mobile API
subzeroid/instagrapi-rest	599	RESTful HTTP wrapper around `instagrapi` for non-Python consumers
subzeroid/aiograpi	346	Async sister project, same API shape — see the comparison
subzeroid/insto	—	Interactive Instagram OSINT REPL with HikerAPI default backend
subzeroid/insta-dl	—	Async Instagram downloader CLI; uses HikerAPI for no-ban backend

instagrapi-rest is the bridge worth pointing out: if your service is in Go, Node, Ruby, or anything other than Python and you still want instagrapi’s endpoint coverage, run instagrapi-rest as a sidecar and call it over HTTP.

CLI and TUI clients

instagrapi is a library, not a CLI — but enough developers want a terminal-native Instagram experience that several substantial CLIs have been built on top of it.

supreme-gg-gg/instagram-cli — 1 888 ⭐. Full TUI client: messages, browsing, posting from the terminal. By stars, the largest single project built on instagrapi.
TnYtCoder/InstaPilot — 64 ⭐. Compact CLI focused on automation: scheduled posts, follow/unfollow rules, batch operations.

OSINT tools

instagrapi’s untyped surface is roughly the same as the Instagram private mobile API, which makes it the natural substrate for OSINT tooling. Several projects in this category are forks or rewrites of Datalux/Osintgram; for a structured comparison see the Osintgram / instagrapi / insto guide.

silverxcyber/SilverInstaEye — 294 ⭐. Comprehensive OSINT toolkit; profile metadata, bio extraction, network mapping.
EchterAlsFake/Osintgram2 — 28 ⭐. Osintgram rewrite using instagrapi instead of the original session-based scraper.
Mohamad-Mortada/Osintgram — 22 ⭐. Maintained Osintgram fork.
vaseesav/insta-mon — 11 ⭐. Single-target activity monitor — track changes to one Instagram account over time.

AI agents, MCPs, and LLM integrations

instagrapi is one of the dependencies AI-agent frameworks reach for when they need an Instagram action surface. The MCP server pattern is showing up here too.

sheet0/npi — 228 ⭐. Action library for AI agents covering many platforms; instagrapi is the Instagram backend.
ranahaani/autogram — 60 ⭐. AI news-curation agent that posts to Instagram autonomously.
philippmoehl/insta-gpt — 36 ⭐. ChatGPT-driven social media manager — comments, replies, content generation.
louistaii/AI-Influencer — 26 ⭐. Pipeline for synthetic Instagram influencer accounts (image generation + posting).
Klaudiusz321/social-media-agents — 24 ⭐. Modular multi-agent system for cross-platform social media work.
taskmaster-ai/insta-mcp — 18 ⭐. MCP (Model Context Protocol) server exposing Instagram operations to LLM clients.
elizaos-plugins/plugin-instagram — 10 ⭐. Instagram plugin for the ElizaOS agent framework.

Cross-platform bridges

A common shape for instagrapi users is “I want Instagram content on a different platform” — repost, embed, or mirror. These projects implement that bridge in different directions.

The-HellBot/HellBot — 601 ⭐. Telegram userbot with instagrapi integration; downloads Instagram content into Telegram chats.
molly/w3igg-crossposter — 45 ⭐. Bridges web3isgoinggreat.com posts to Instagram and other social networks.
PatrickAcheson/automate_youtube_shorts — 35 ⭐. End-to-end Instagram → YouTube Shorts pipeline.
chdlc/instagram-to-telegram — 20 ⭐. Mirrors latest Instagram posts into a Telegram channel.
sb0y/warp_beacon — 19 ⭐. Telegram bot that downloads from YouTube, Instagram, TikTok via a single interface.
amadejkastelic/discord-video-embed-bot — 18 ⭐. Discord bot that auto-embeds Instagram (and other platform) videos. Notable as the largest project that uses aiograpi rather than instagrapi.
kanewi11/telegram-reposter — 18 ⭐. Auto-repost from Telegram to Instagram and VK.

Account automation

The bulk of the instagrapi long tail is account-automation tooling — follower growth, engagement automation, content scheduling. Read the README before running any of these against an account you care about.

new92/igfi — 296 ⭐. Instagram followers increaser.
Avnsh1111/Instagram-Reels-Scraper-Auto-Poster — 296 ⭐. Reels scraper + auto-poster pipeline.
new92/instatools — 294 ⭐. Multi-purpose automation toolkit.
TnYtCoder/InstaFans — 107 ⭐. Follower growth script.
new92/iam — 50 ⭐. Account manager — multi-account orchestration.
qxxa/instahunt — 39 ⭐. Username autoclaimer / swapper.

How this list was built

The list comes from GitHub’s /network/dependents page for subzeroid/instagrapi, which surfaces every public repository that declares instagrapi in a parseable dependency manifest (requirements.txt, pyproject.toml, setup.py, or Pipfile). The fetcher walks that page’s pagination, then enriches each repository with star count, primary language, last push date, and archival status via the GitHub GraphQL API. The full snapshot is stored in this site’s source tree at src/data/dependents.json. Refresh with python3 scripts/fetch-dependents.py > src/data/dependents.json. The snapshot above was generated 2026-05-02 against 2,964 dependent repositories, of which 1,322 returned successfully (the gap is private, deleted, or renamed repos).

Two caveats worth restating. First, this is instagrapi only — aiograpi (the async fork) has its own much smaller dependents list (11 enriched at snapshot time, top of which is amadejkastelic/discord-video-embed-bot at 18 ⭐). Second, “uses instagrapi” is not “uses instagrapi well.” Star count is a popularity proxy, not a quality or maintenance signal — check last-commit date and issue health before pulling any of these into a production stack.

Wrapping up

If you’re evaluating instagrapi and want signal beyond the project’s own README, this is the long answer: more than a thousand public repos depend on it, the top are real CLIs, OSINT toolkits, and AI agents with active communities, and the spread of use cases — from terminal clients to MCP servers to bot frameworks — is broader than any single tutorial conveys. If you’re already using instagrapi and have built something worth seeing, get your repo public with instagrapi in the manifest and it will surface in the next refresh.