Drop-in widget
One script tag on your blog template; every article auto-generates a video player at the top.
TC00:00:00:00SOLUTION · LIVE
SOLUTION · CHANNEL · 08
Drop a script tag. Every blog post gets a video.
Engineering teams at CMS-driven sites use VideoCue as infrastructure. One snippet on your blog template; every article auto-generates a video preview.
WHO IT'S FOR
Engineering lead at a content-driven company — CMS startup, dev-marketing team, headless publisher, B2B blog. You want video as a feature without building the pipeline.
THE BOTTLENECK
Your content team writes great articles. Video would boost dwell time + SEO + social shares. But building a video generation pipeline is six months of engineering work — and isn\'t your core competence.
WHAT YOU GET
The outputs that actually matter.
REST API
Full programmatic control — POST a script, get back an MP4 URL + thumbnail + caption file.
Webhook-driven
Article publishes → VideoCue receives content → video URL posts back. Zero polling.
CMS integrations
WordPress plugin + Shopify app shipped. Ghost / Webflow / Sanity documented as webhooks.
Layered key security
Publishable keys check the Origin header AND carry a hard monthly cost cap, per-key rate limit, and one-click revoke. Same model Stripe + Mapbox use. Abuse-bounded, not magic.
Cost controlled per-key
Set per-key monthly budgets. We refuse generations when caps are hit — no surprise bills.
HOW IT WORKS · ONE WEEK
From brief to published.
F-01
API key
Generate a publishable key, allowlist your domain.
F-02
Integrate
Drop the widget script OR call our REST API.
F-03
Webhook
Article publishes → VideoCue generates → callback fires.
F-04
Embed
iframe player on your article; first load shows progress, then plays.
RECOMMENDED PLAN
Built for the Studio (with API + widget) tier.
See full pricing, included quotas, and overage rates.
See pricing →FAQ
Questions buyers actually ask.
Is the widget CSP-friendly?
Yes — single sandboxed iframe pointing at our CDN. No DOM access on the host page. We publish Subresource Integrity hashes per version.
How are API keys secured? Can someone scrape my key and abuse it?
Honest answer: no client-side key is unhackable — the Origin header that locks publishable keys to your domain CAN be spoofed by a server-side actor with curl. What stops abuse in practice is the layered defense: (1) Origin check blocks browser-based misuse, (2) per-key monthly cost cap means even a scraped key can't run up your bill, (3) 100/hour rate limit caps fast burn, (4) instant revoke from your dashboard kills any leaked key, (5) anomaly detection flags 10x spikes. Same model Stripe, Mapbox, and Algolia use for their public keys. For anything sensitive — read user data, configure webhooks, programmatic destination publishing — use server-only secret keys instead.
What happens if my widget gets a traffic spike?
Cached by content-hash — same article hits cache. Beyond the cache, your per-key monthly budget gates new generations.
Self-hosted option?
Not yet. We're cloud-only for the rendering pipeline; you embed our iframe. Self-hosted is on the roadmap for enterprise.
Pricing for high-volume sites?
Default is $0.50/generation overage above Studio's 100 included. Sites doing 10k+/month, contact us for negotiated rates.