Canva Craft (2K, API, MCP): a fourth SaaS leg for Bubble bulk catalogs alongside BIAIG orchestration

Why this shows up in October digests

October roundups keep pairing Canva Craft (2K, API, MCP) with COGS talk around frontier and chatbot image APIs. OpenAI shut down gpt-image-1 on 2026-10-23, so I see founders reopening default routes for mass-generation—where to render the asset vs where to hold the catalog.

On the editorial arc: an internal 29 Oct cutover for Nano Banana 2 (gemini-3.1-flash-image) is not in Google’s official changelog (2026-10-06: model deprecated, no shutdown date announced). I do not treat 29 Oct as vendor fact. A closer look: 29 Oct 2026 Nano Banana.

What primary sources say about Craft

• Product: Canva Craft is Canva Research’s first in-house image model (newsroom, Oct 22 2026 context): two-stage planning → rendering, up to 2K, 30+ aspect ratios, design templates, legible text, Magic Layers compatibility.
• Connect API (preview): craft_v1_2k via async POST /v1/image-generations + polling; typical job time ~50–60 s; output is a 24-hour download URL or Canva upload; requires a user access token with asset:write; jobs consume the user’s AI credits (dev community thread + REST reference).
• MCP: Canva MCP Server went GA 2026-10-07 (OAuth, per-user). It exposes generate-image, but the Craft dev thread states “Craft on the Canva MCP Server is coming soon.” Newsroom copy mentioning MCP alongside Craft is wording, not proof that MCP already pins craft_v1_2k.
• COGS narrative (press, not API list pricing): Forbes Australia quotes Cliff Obrecht on slowing rollout after Create due to frontier cost, and ~90% cost-to-serve reduction after in-house work. No absolute $/image for Craft in primary API docs—only relative press comparisons.

“Fourth SaaS leg” and BIAIG—editorial framing only

BIAIG and “fourth SaaS leg” do not appear in public vendor documentation. They are this publication’s internal label for bulk AI-image pipelines in Bubble (alongside October legs such as OpenAI Image, Gemini image, FLUX/BFL). Do not present them as Canva or Bubble official terms. Same topic: ShaheerTools free bulk guide (17.

Split “design in Canva” from “catalog in Bubble”

Concern	Canva (Craft / API / MCP)	Bubble (BIAIG + API Connector)
Generation / editable design	Craft, Magic Layers, design export	—
Async orchestration	POST + poll; MCP generic image tools	Backend workflows, queues, backoff, idempotency
Durable asset URL	24h download URL → must ingest	Permanent URL on the SKU row
Multi-tenant bulk	Per-user OAuth; user credits	Privacy rules, roles, tenant isolation
Catalog state machine	—	queued / generating / stored / failed

Canva does not replace your data layer. Who sees which SKU and who pays for credits stays in Bubble plus your OAuth policy.

Practical Bubble developer pattern

1. Model leg: For explicit craft_v1_2k, I use Connect API preview today—not MCP—until Craft on MCP is documented.
2. API Connector: Chain create job → poll → on success read URL; I avoid tight polling without backoff (~50–60 s × N SKUs hits rate limits and credit caps).
3. Ingest immediately: On success, download → upload to your storage → write the permanent URL to the catalog row; otherwise the Canva leg expires in 24 hours.
4. OAuth shape: asset:write per user is harder for multi-tenant bulk than server-key image APIs; I treat shared “design ops” account vs per-merchant OAuth as a product call—not docs-only.
5. Preview risk: Generations API is preview—breaking changes possible; public apps on preview do not pass review.
6. Product fork: Editable design (Magic Layers) vs flat PNG bulk catalog determines whether you need full Canva design export or generations alone.

October routing context (source-bounded)

• OpenAI: gpt-image-1 shut down 2026-10-23; replacements include gpt-image-2.5-flare / gpt-image-2.5-sunburst.
• Google: Nano Banana 2.1 GA 2026-10-06; gemini-3.1-flash-image deprecated, shutdown TBD.
• BFL: FLUX 3 Image API—early-Oct promo arc per release notes; separate from Canva economics.

Craft is a fourth external leg in the sense of “another SaaS destination for bulk prompts,” not a substitute for Bubble-side orchestration.

Open questions (do not invent answers)

• MCP ship date and model selector for Craft / craft_v1_2k.
• Connect generations exiting preview; developer-funded billing vs user credits (community thread: “confirm”).
• Official API unit economics outside the user credit pool.
• Batch concurrency at ~50–60 s per job.

What I actually wire

I put Canva Craft where 2K, template-aware, design-native output matters—via Connect API preview. Bubble stays the system of record for SKU rows, privacy rules, batch orchestration, and permanent storage. MCP stays in backlog until dev-community confirms Craft on the server. Canva’s COGS story explains why the model exists; my Bubble P&L stresses latency, OAuth, 24h URLs, and preview stability—not press percentages without list pricing.