$500 a month for a dashboard you barely open.
Hootsuite, Sprout, Later. Per-seat pricing for a posting calendar and a chart. Your team uses 10% of it, every month, forever.
The API for building Instagram features · beta open
Build Instagram features for your / team team /
One API plus an MCP server your agent can drive. Type any feature your team, SaaS or agency clients need. We’ll write the build prompt for you.
// build your Instagram feature powered by InvisibleAPI MCP
// building for
Built by teams shipping Instagram features in-house, inside their SaaS, and for their clients
Pulse.ai
Northwind
Cortex/OS
Beacon
Loop·Studio
Holdfast
Why you need it
Still using the same old, limited Instagram tools? /Time to build your own/.
In-house tool, embedded in your SaaS, or shipped to your clients. Anyone who’s tried to build on Instagram has run into the same wall.
Your campaign data lives in someone else's UI.
Want to ask your own data a question? Export a CSV, open it in Sheets, copy a number into a doc. Your numbers are not really yours.
Every workflow you actually need is "on the roadmap."
UGC reposts with credit. Comment triage by Claude. Top hashtag picks from your own posts. The vendor will ship it in Q3. Probably.
Six Zapier zaps held together with hope.
You built around the SaaS. A scraper here. A webhook there. A Make scenario your ops lead is scared to touch. One Meta change away from breaking.
Multi-platform tools post everywhere. None run Instagram well.
Ayrshare and friends flatten Instagram into a lowest-common-denominator post button. No Stories logic, no mention recipes, no real metrics.
What you can build
Six features your team can /ship this week/.
Click a tile to preview the screen. UGC reposts, comment triage, an analytics dashboard, anything you can name. Built with our blocks. Owned by you.
Scheduled posts6 queued
| Post | Schedule | Platforms | Status |
|---|---|---|---|
| pst_8KZx2qLmR3 | May 16 · 10:00 |  | queued |
| pst_8KZx2qLmR4 | May 16 · 14:30 | | live |
| pst_8KZx2qLmR5 | May 17 · 09:00 | | queued |
| pst_8KZx2qLmR6 | May 17 · 11:15 | | retry · 2 |
| pst_8KZx2qLmR7 | May 18 · 08:00 | | queued |
UGC approval inbox12 pending
@maria.ktagged you in a Story · "love the new launch ✨"
@runner.dantagged you in a Reel · "best running app on the market"
@lina.designstagged you in a Story · "obsessed with this packaging"
@kemi.osuntagged you in a Reel · "review coming this week"
Comment reply drafts8 awaiting
"when does this drop in EU?"AI draftShipping to EU on June 5. Thanks for the heads up!
"do you ship to Mexico?"AI draftYes. Mexico shipping is live. Order by Sunday for next week.
"how do I get a discount code?"AI draftSending a code over DM right now ✨
This weeklive
Engagement rate5.4%+0.9
Reach142K+18K
Follower delta+412+8%
Top postpst_8KZx
Tagged mentionstoday
@city.runner"finally a running app that gets it"positive
@maria.k"new packaging is gorgeous, can't wait"positive
@oscar.b"shipping took too long, disappointed"routed to Slack
@jules.k"is the new bottle BPA free?"question
Failed posts2 need attention
| Post | Reason | Retry | Status |
|---|---|---|---|
| pst_x88dQ12 | media.timeout | 2 of 3 | retrying |
| pst_p44Hk88 | scope.missing | — | needs human |
| pst_z11Bn7q | caption.length | 3 of 3 | recovered |
| pst_w52Lp1a | media.format | 1 of 3 | retrying |
Or read the MCP docs and wire it yourself.
What you get
The pieces you need to ship /any Instagram feature/.
Three building blocks. One API. One MCP server. One bill. Publish to Instagram, listen back with computed metrics, plug the whole thing into your agent.
Publish.
Reels, Stories, carousels, feed posts, comments. Scheduled or instant. Validated before they ship, retried when Meta blinks.
- POST /publish/reel
- POST /publish/story
- POST /publish/carousel
- POST /publish/comment
Listen.
Posts, comments, tagged mentions, account insights. Plus computed metrics: best times to post, top hashtags from your own data, top post of the week.
- GET /mentions
- GET /comments
- GET /analytics/posts
- GET /metrics/best-times
Plug into AI.
Every endpoint exposed as a typed tool. Claude, ChatGPT, Cursor, n8n, Make. Point your agent at one URL and let it drive.
- tool publish_reel
- tool reply_to_mention
- tool suggest_best_time
- tool recover_failed_post
// platforms covered
Instagram api.invisibleapi.ai/v1/*
Live 
TikTok same endpoints, different surface
Coming soon 
X same endpoints, different surface
Coming soon 
Google Business same endpoints, different surface
Coming soon
How it works
Anatomy of a /UGC repost/.
A customer tags you in a Story. Six endpoints run in order: catch the mention, fetch the media, queue for approval, validate, publish, and send a confirmation webhook back. The failure path is built in.
Recipe: UGC repost · mention to confirmation, in six steps
01 · trigger HOOK mention.tagged
Your customer tags you in a Story. A signed webhook lands in your stack.
02 · enrich GET /media/{id}
Pull caption, dimensions, owner, permissions. Decide if it's repostable.
03 · queue QUEUE approval.queue
Drop it in an approval inbox. Your team or your agent picks it up.
04 · validate POST /publish/dry-run
Caption length, media format, scope checks. Catch the bug before Meta sees it.
05 · ship POST /publish/story
Idempotency key, retry with backoff, dead-letter on terminal fail.
06 · confirm HOOK post.published
Signed webhook fires back with media_id, permalink and timing.
FAIL post.failed fires with reason.
media.timeout, scope.missing, etc. Your stack decides to retry, alert, or queue for human review.
Why us
15 years on Instagram's API. /We've got you/.
Built by EmbedSocial. Shipping social APIs in production since 2010. The building blocks we hand you are battle-tested against every Meta change since then.
Doing the thing
InvisibleAPI
Big SaaS (Hootsuite, Later)
Onboard a client account
●OAuth in your own UI. Tokens stay healthy. No seat for the client.
○Their UI. Their seat. $79 per month, per client.
Repost UGC to a Story
●A named recipe. Drop in, ship by Friday.
○On the roadmap. Coming Q3. Probably.
Ask "what's our best time to post?"
●One API call. Computed from your own data. Your agent reads it.
○A chart in their dashboard. Open the tab. Take a screenshot.
Reply to mentions with Claude
●
reply_to_mention MCP tool. Your agent does it overnight.○Manually, with your team's Monday morning.
When Meta changes the API
●We absorb the change. Your code doesn't move.
○They ship a fix. You hope it lands by Tuesday.
Own your data
●It lives in your stack. Query it any way.
○It lives in their DB. Export CSV and good luck.
Big SaaS gives you their dashboard. Generic APIs flatten Instagram. We hand you the building blocks, so you can ship Instagram features. For your team, for your SaaS, or for your clients.
Pricing
Pay for volume, not features. /Drag to find your plan/.
Tell us how many accounts you'll connect and how many reads you need each month. We'll show you the right tier.
// Connected accounts 10
11050250300+
// Reads / month 50K
1K50K500K5M6M+
POPULAR
// Starter
$19/mo
First brand, first recipes shipping in-house.
Accounts10
Publishes / mo2,000
Reads / mo50,000
MCP serverIncluded
Publish = one POST to an Instagram surface. One call, one count.
Read = one GET. Computed metrics inside the response are free.
Overage bills at the next tier's per-unit rate. No surprise invoices.
Every plan includes publishing, reads, MCP, webhooks, audit log.
Honest answers
Things you're about to ask.
No. It helps if you’ve built things in Zapier, Make or n8n. For everything past that, Claude or Cursor will write the wiring for you. The MCP server is the point: your agent drives the API.
Pay if their dashboard does what your team needs. Most teams use 10% of what they pay for, hit a wall on workflow #4, and Zap their way around it. We hand you the building blocks instead. You own the stack.
Doing Instagram well is more than enough work for a whole product. Every platform has its own quirks. We expose Instagram’s rules rather than flattening them into a lowest common denominator. If you need TikTok or LinkedIn alongside, run them in parallel.
Out of scope by design today. The endpoint shape is platform-neutral, so when we expand we’ll add them under the same auth and runtime. We’d rather ship Instagram end to end than five platforms half way.
Within Meta’s rules: yes, but only within the 24 hour window after the user starts the message, and beyond that only with approved message templates. Our reply_to_mention tool checks both and falls back to a draft if the window is closed.
We absorb the change. Your code doesn’t move. Breaking changes upstream become non-breaking for you. That’s the whole point of running Instagram on a managed stack instead of against the raw API.
Yes. Business or Creator, linked to a Facebook page. Permissions needed: instagram_basic, instagram_content_publish, instagram_manage_comments, instagram_manage_insights, pages_show_list. Our onboarding asks for them in one screen.
Yes. Meta caps publishing at 50 posts per 24 hours per account, and the read API has its own per-app quota. We surface usage live and queue overflow gracefully. You will never accidentally burn an account by spiking.