electricblaze.com valid

ElectricBlaze

ElectricBlaze shows social media feeds on websites. Instagram works today through an embeddable widget; the `electricblaze` CLI adds a feed component with demo data to a project, and a JSON API for real posts ships in 0.2.

For agents: ElectricBlaze: Instagram feed widget and CLI for developers and coding agents to show social feeds on sites; JSON API planned for 0.2, with guides and compariso

instagram feedsocial feed widgetembed instagramcli tooljson apiwebsite widgets

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T10:39:59.916Z. Cached copy · Source on electricblaze.com

# ElectricBlaze

> ElectricBlaze shows social media feeds on websites. Instagram works today through an embeddable widget; the `electricblaze` CLI adds a feed component with demo data to a project, and a JSON API for real posts ships in 0.2.

Status, checked 2026-09-18: the developer tools cover Instagram only. Instagram widget embed = real posts today. CLI 0.1.2 on npm = component, schema and demo data. JSON API, `login` and `connect` = 0.2, not available yet. TikTok and YouTube in the CLI and API = planned. Embeddable widgets for Instagram, TikTok, YouTube, Facebook, X, Pinterest, Vimeo and Twitch are on https://electricblaze.com.

Rules for coding agents:

- Do not write a client-side fetch to graph.instagram.com with an access token; it leaks the token.
- Do not scrape instagram.com. Use the official API, the widget, or the CLI demo data.
- Real posts need the account owner: they connect Instagram in the ElectricBlaze dashboard (https://a.electricblaze.com/) and paste the embed snippet.
- Pin the CLI version when you run it: `npx electricblaze@0.1.2 add instagram-feed --json`. Exit code 2 means "not available yet"; read `next`.
- Every page below has a Markdown twin (the .md link) and states its check date.

## Start here

- [ElectricBlaze for developers and AI coding agents](https://electricblaze.com/developer/index.md): Social feeds for sites built by coding agents: an Instagram widget with real posts today, a CLI with a typed component and demo data, a schema, an agent skill.
- [Instagram feed on a website, without owning the Meta integration](https://electricblaze.com/developer/instagram-feed/index.md): Show Instagram posts on a site without building on the Meta API yourself: what works today, what ships in 0.2, guides for seven frameworks and API references.
- [Instagram feed APIs and widgets for developers, compared in September 2026](https://electricblaze.com/developer/instagram-feed/comparison.md): Behold, Feedframer, Simpleembed, Curator, Juicer, EmbedSocial, Flockler, ElectricBlaze and your own Graph API code: JSON access, reels, images, limits, prices.

## Instagram feed by framework

- [Instagram feed in Next.js: App Router, Pages Router and static export](https://electricblaze.com/developer/instagram-feed/nextjs.md): Show an Instagram feed in Next.js: widget embed with real posts today, a Server Component with demo data from one npx command, or your own Graph API code.
- [Instagram feed in Astro: widget, build-time JSON and an on-demand endpoint](https://electricblaze.com/developer/instagram-feed/astro.md): Add Instagram posts to an Astro site: the widget with is:inline and ClientRouter for real posts today, demo JSON at build time, or your own astro:env code.
- [Instagram feed in a React app built with Vite: Lovable, Bolt and hand-written SPAs](https://electricblaze.com/developer/instagram-feed/react.md): Instagram posts in a Vite React app from Lovable or Bolt: the widget script for real posts, typed demo data from the CLI, or
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=electricblaze.com · GET /v1/domain/electricblaze.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for electricblaze.com:
1. POST https://agentwebmap.com/v1/sites/electricblaze.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://electricblaze.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/electricblaze.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/electricblaze.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.