Choose a model
- Identify the task: image generation/editing, text/image-to-video, music, or speech. Specify count, quality, duration, references, and budget.
- Query the account-available catalog, use its exact model ID, and inspect the schema. Family names, aliases, and display names are not automatically submission IDs.
- Compare suitable newer or recommended families, then explain quality, reference support, cost, and expected wait. Do not claim measured popularity without platform statistics.
- Check required fields, ranges, and mutually exclusive inputs before estimating the final request. Reconfirm after changing models or inputs.
Read an estimate
Check
input_valid, problems, basis, and warnings. Catalog starting prices are not complete request quotes. Resolution, sound, references, actual input duration, and audio billing methods can affect costs.
Released clients mainly use public default prices, not complete account discounts, measured usage, or account-settlement Quotes. New endpoints or code candidates do not establish production adoption. Pause when pricing or budget comparison is incomplete. The reference conversion is about 68 credits per $1; use actual responses and account records.
Approval and budgets
Show the exact model, final inputs, output specifications/count, estimated cost, and limitations. Obtain explicit approval for this generation. Changes to model, references, inputs, identity, price, or an expired quote require a new estimate and approval.
These are separate checks. Sign-in and host permission do not approve a charge. Do not remove budgets, change Keys, or switch routes to bypass rejection. Final caps require corresponding server support; current documentation cannot promise settlement never exceeds an estimate budget.
CLI stores a local
quote_id and submits with --confirm. Native MCP keeps inputs, estimates, and explicit approval in the agent workflow; it has no CLI quote file or session-level server approval button. See CLI approval and MCP approval.
Permissions, balance, and quotas
Same-account CLI and remote MCP OAuth can currently share internal Key permissions, quotas, and paused status. Changes affect its consumers, while CLI and host sessions remain separate. Local stdio uses its configured personal API Key. Model, balance, and task queries do not submit media generation. Generation is billed; uploads have separate file-service limits. Resolve insufficient funds, quota, or access in the relevant account settings. Reauthentication cannot add funds or unpause a Key. Failure, timeout, sign-out, or closing a page do not establish no charge or a refund. Report billing conclusions only from explicit evidence; usage queries are not complete statements.Empty search, invalid inputs, or incomplete pricing
- Broaden wording while retaining required task/reference capabilities; check account and permissions.
- Read this model’s schema again and check fields, enums, ranges, and mutually exclusive references.
- Estimate final inputs and follow the status table. Do not fill unknown factors with starting prices.
- Reconfirm requests not yet submitted. For submitted or unknown requests, recover first.