Luma AI through Squiid

What Luma AI is

Luma AI serves the Dream Machine video models and the Photon image models through a developer API. Generations can be driven from a prompt, from a start or end keyframe, or from an existing clip you want extended, and the API supports looping, aspect ratio selection and reference images for consistency between shots. Jobs return a state you poll, and generations can be chained so the last frame of one clip becomes the first frame of the next.

For an app built with coding agents, Luma is one of the two or three realistic options when a feature needs moving pictures rather than stills. It shows up in social content tools, listing and catalog animations, and creative products where a user supplies an image and gets a few seconds of motion back. The integration shape is the same as any other heavy media API: submit, wait on a callback, store the output, serve it from a CDN. Because model behaviour differs noticeably between video providers, teams often keep two connected and route by prompt type.

Why connect it through Squiid

Luma AI is on the Squiid roadmap. When it is live, requests will go to https://api.squiid.io/v1/luma-ai/... with Authorization: Bearer $SQUIID_API_KEY, the official SDKs will work by pointing their base URL at the gateway (gateway convention), and generations will be metered against your prepaid credits at Luma's list price. Squiid will hold the upstream key, so an agent can add a video feature without writing a provider credential into your environment, and the spend will arrive on one monthly invoice with the storage and hosting the same feature needs.

• One account, one key, one bill, one dashboard. Luma AI sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Luma AI credentials. Your code carries SQUIID_API_KEY, so LUMAAI_API_KEY, LUMA_API_KEY, LUMA_BASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Luma AI costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Dream Machine video generation through the gateway
• Photon image models on the same key
• Keyframes, extensions and reference images
• Usage metered against prepaid credits
• Luma list pricing, no markup

How to connect Luma AI

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces LUMAAI_API_KEY, LUMA_API_KEY, LUMA_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/luma-ai/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Luma charges per generation based on model, resolution and duration, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Luma AI usage, with no markup and no per-request margin.

Luma AI has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Luma AI usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Luma AI is usage-metered, so leaving means creating your own Luma AI key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Luma AI's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Luma AI through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Luma AI usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.