← Search

Instagram data API via fetcher.sh
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit d7e88be
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : uses API keys or tokens
⚙ Needs: fetcher.sh credits…

Instagram data API via fetcher.sh

Pull Instagram profiles, posts, reels, stories, followers, comments and hashtag/location/audio feeds — one plain HTTP GET per call, no login, no headless browser

At a glance
What
Pull Instagram profiles, posts, reels, stories, followers, comments and hashtag/location/audio feeds — one plain HTTP GET per call, no login, no headless browser
Cost
Free
Needs
fetcher.sh credits — a Bearer API key (bby_live_...) from https://fetcher.sh/topup, or an x402-capable setup to pay per call in USDC; $0.004 per call, no free tier, no refunds on upstream failures; curl or an HTTP client
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Instagram data API via fetcher.sh is a free Muse skill that pulls Instagram profiles, posts, reels, stories, followers, comments and hashtag, location and audio feeds through one plain HTTP GET per call, with no login and no headless browser. Every call uses the paid fetcher.sh API, billed per call in prepaid credits or USDC settlement, with no usable free tier.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit d7e88be

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: fetcher.sh credits — a Bearer API key (bby_live_...) from https://fetcher.sh/topup, or an x402-capable setup to pay per call in USDC; $0.004 per call, no free tier, no refunds on upstream failures; curl or an HTTP client Install "Instagram data API via fetcher.sh" for me. It gives the agent @fetcher-sh's playbook for pulling Instagram data with one plain HTTP GET per call against https://instagram.fetcher.sh — no login, no session cookies, no headless browser: 16 endpoints covering profile lookup by @handle, account search, posts/reels/stories/tagged posts/followers/followings by user id, post lookup by shortcode, comments, hashtag and reel-only hashtag feeds, location posts, and audio-track posts — plus the MCP server setup (free discovery tools, paid fetch_data) and error semantics. Repository: https://raw.githubusercontent.com/fetcher-sh/fetcher-skills/d7e88be6e1210bae14803dcb435e19d36cf8a17c/skills/instagram-api/SKILL.md Pinned version: install the code at commit d7e88be6e1210bae14803dcb435e19d36cf8a17c exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "instagram-api". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. get a fetcher.sh API key and save it in the vault — never paste it into prompts). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It works with an API key or a token that you provide.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit d7e88be · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : uses API keys or tokens
What the scan found — excerpts from the install prompt
  • uses API keys or tokens — Prerequisites: fetcher.sh credits — a Bearer API key (bby_live_...) from https://fetcher.sh/topup, or an x402- · Prérequis : crédits fetcher.sh — une clé API Bearer (bby_live_...) depuis https://fetcher.sh/topup, ou une con
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
d7e88be · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : uses API keys or tokens

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.