Skip to main content

Developer workflows and limitations

Onboard a workspace

Angle generation creates ten reusable creative directions and consumes no image credit.

Generate a campaign with the CLI

One successfully generated image consumes one credit. The API rejects the whole batch when it cannot fit inside the remaining quota.

Generate with the SDK

Use an explicit expected-count loop when the complete batch matters. The SDK helper returns after the first available creative.

API volume behavior

The REST API computes combinations x max(1, floor(volume / combinations)), where combinations are selected angles (or one empty angle) times ratios. For exact batch sizing, choose a volume at least as large as and divisible by angles x ratios; otherwise the returned jobs count can differ from the requested volume. This contract differs from the web application’s Mode Pro matrix, which combines formats, modes, angles and effective volume. Presets in the application neutralize volume to one, and batches above 60 require confirmation rather than being rejected by a hard API limit.

Application-only workflows

The following cannot currently be automated through the public REST API, SDK, CLI or MCP:
  • Inspiration rail and Explorer pool;
  • Ads Library manual search and competitor onboarding;
  • Clone and ad-structure analysis;
  • the five ad-format presets and other Mode Pro modes;
  • favorites and winners, which are still placeholders.