At a glance
Status, checked 2026-09-18: the developer tools cover Instagram only. The Instagram widget embed shows real posts today. The electricblaze CLI 0.1.2 on npm adds a component with demo data; its JSON API ships in 0.2. TikTok and YouTube in the CLI and API are planned.
- Use it when
- you are an agent or a developer adding a social feed to a site and want a working grid now, real posts without a Meta app, and a data contract that will not change under you.
- Do not use it when
- you need TikTok or YouTube data in code today, or a public Instagram JSON feed today. Neither exists yet; the comparison names providers that have the latter.
- What the human does
- connects the Instagram account in the dashboard at a.electricblaze.com when real posts are needed. Everything else can be done by an agent.
- Next step
- start at the Instagram feed hub or run
npx [email protected] add instagram-feed --json.
Start here
- Instagram feed hub: what works today, framework guides, API reference.
- Compare Instagram feed providers: nine options with dated facts, including where we are behind.
- Next.js guide, the most common stack for agent-built sites.
- The CLI and the agent skill.
Install in one line
| What | Command |
|---|---|
| Component and demo data | npx [email protected] add instagram-feed --json |
| Agent skill for Claude Code and Codex | npx electricblaze skill |
| Agent skill for any agent | npx skills add ElectricBlaze/electricblaze |
| Through shadcn | npx shadcn@latest add ElectricBlaze/electricblaze/instagram-feed |
| Claude Code plugin | /plugin marketplace add ElectricBlaze/electricblaze |
| Real posts today | Paste the widget snippet from the dashboard |
Widget snippet (the id comes from the dashboard)
<div class="electricblaze-id-WIDGET_ID"></div>
<script src="https://s.electricblaze.com/widget.js" defer></script>For agents: files you can fetch
Every page in this section exists twice: as HTML and as Markdown. Add .md to the address, or send Accept: text/markdown to the HTML address.
Machine-readable entry points
{
"llms_txt": "https://electricblaze.com/llms.txt",
"llms_full_txt": "https://electricblaze.com/llms-full.txt",
"markdown_twin": "https://electricblaze.com/developer/instagram-feed/nextjs.md",
"feed_schema": "https://electricblaze.com/developer/instagram-feed/schema.json",
"sample_feed": "https://electricblaze.com/developer/instagram-feed/sample-feed.json",
"changelog_atom": "https://electricblaze.com/developer/changelog.xml",
"npm": "https://www.npmjs.com/package/electricblaze",
"source": "https://github.com/ElectricBlaze/electricblaze"
}Each page starts with a status line and its check date. Facts about Meta's API carry a link to the page they came from and the date it was read.
Rules we ask agents to follow
- Do not write a client-side fetch to graph.instagram.com with an access token; it leaks the token to every visitor.
- Do not scrape instagram.com. Use the official API, the widget, or the CLI demo data.
- Real posts need the account owner. Say so, and hand them the link to the dashboard.
- Pin the CLI version and read
nextin the JSON output. Exit code 2 means "not available yet", not failure. - Keep the "demo feed" label until real data flows. A grid of sample posts must not pass for the client's account.
What we are and are not
ElectricBlaze started as embeddable social widgets. We are building a data layer for feeds on top of them: one schema for every network, with the platform APIs, tokens and caching on our side.
Today the developer tools cover Instagram. Widgets for other networks are on the main site and are outside this section. Where a page here says "0.2" or "planned", the thing does not exist yet.
Source code of the CLI, the schema and the skill: github.com/ElectricBlaze/electricblaze, MIT license. Security reports: [email protected].