Stability AI through Squiid

What Stability AI is

Stability AI publishes the Stable Diffusion and Stable Image model families and serves them from its own platform. Beyond text to image, the API includes a set of editing operations that are usually the harder part to build: inpainting and outpainting, background removal and replacement, search and replace by prompt, structure and style controls, and creative upscaling. There are also audio and 3D models in the catalog. Requests are priced in credits per operation, so an upscale, an edit and a generation each carry a different cost that is worth checking before you loop over a catalog.

In an AI-coded product these endpoints cover the editing half of a media feature. Generating a picture is easy; letting a user remove the background, extend the canvas to a different aspect ratio, or replace one object in an existing photo is where most projects stall. Because Stability also releases open weights, teams sometimes prototype on the hosted API and move to self-hosted inference once volume justifies it. Control endpoints that condition on sketches or depth maps are what let a design tool keep layout fixed while the style changes.

Why connect it through Squiid

Stability AI is on the Squiid roadmap. When it is connected, requests will go to https://api.squiid.io/v1/stability-ai/... with Authorization: Bearer $SQUIID_API_KEY, the official SDKs will work by pointing their base URL at the gateway (gateway convention), and generation credits will be metered against your prepaid balance at Stability's list price with no Squiid markup. The upstream key will stay in Squiid's custody, so an agent can add image editing to a project without a credential ever being written into the repository, and the spend will appear on the same invoice as your other services.

• One account, one key, one bill, one dashboard. Stability AI sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Stability AI credentials. Your code carries SQUIID_API_KEY, so STABILITY_API_KEY, STABILITY_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 Stability 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

• Stable Diffusion image generation through the gateway
• Inpainting, outpainting and background removal
• Upscaling and structure control on one key
• Usage metered against prepaid credits
• Stability list pricing, no markup

How to connect Stability 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 STABILITY_API_KEY, STABILITY_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Stability AI charges credits per generation or edit, with the credit cost varying by model and operation, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Stability AI usage, with no markup and no per-request margin.

Stability 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 Stability 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: Stability AI is usage-metered, so leaving means creating your own Stability AI key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Stability 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

Stability 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 Stability 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.