Signed AI generation quotes before credits move
A signed AI generation quote locks route identity, model options, rate-card version, credit charge, expiry, and signature before reservation—so credits move only on the approved envelope.
A signed AI generation quote is a pre-execution integrity object, not a marketing price list and not a payment authorization. It answers one operational question: which eligible route, model options, rate-card version, and credit charge will apply if the job starts now—and can that envelope still be trusted when reservation happens a moment later.
OfflineCreator’s documented router treats the quote as the lock step between route selection and credit movement. The signed quote records the selected route, options, rate card, credit charge, and expiry before credits move. Changing a model or material option requires a fresh quote, and the reserved charge must match the quote that was approved.
That lifecycle is the ownership of this page. Subscription tiers, credit-pack checkout, and card authorization belong elsewhere. The useful evaluation is whether quote integrity survives option edits, expiry, signature checks, and reservation—not whether a plan page looks inexpensive.
- Before credits move
- Quote first, reserve secondThe signed envelope is created and approved before reservation binds account credits to the generation.
- Integrity object
- Route, options, rate card, charge, expiryA useful quote names what was selected and how long that selection remains valid.
- Fresh quote on change
- Option edits invalidate the prior lockDocumented OfflineCreator behavior requires a new quote when the model or material options change.
Failure modes when the quote is not a hard contract
Community retrieval for this query was thin and often lexical: inspirational “AI quote generators,” policy petitions that happen to say “signed,” and generic credit-runout clips. The usable signal is simpler. Practitioners still report wasting generation credits when duration, resolution, or retry behavior is unclear before spend, and adjacent tooling experiments with signed receipts for agent actions. Those anecdotes do not prove OfflineCreator outcomes; they explain why a mutable estimate is a weak substitute for a signed, expiring quote.
External provider docs show related but different cost timing. fal documents prepaid credits drawn down for successful outputs and notes that costs can be estimated before a request, while also stating that prices vary by model and may change. OpenRouter documents post-request cost calculation from provider token totals with credit deduction after the call. Those are category contrasts, not Offlinecreator pricing claims.
The distinctive OfflineCreator failure mode is a quote that looks current but is no longer binding: options changed after issue, the five-minute signature window expired, the rate-card version no longer matches, or reservation is attempted against a tampered token. In the documented contract, those cases require a fresh quote rather than silently widening the charge.
- Expired signature window
- Five-minute signed selectionProvider-routing docs state the selection is signed for five minutes before reservation uses that envelope.
- Mutated options
- Fresh quote requiredA later duration or resolution change is a new request shape, not a patch on the old signed charge.
- Post-hoc debit contrast
- Not the same as a pre-lockProvider docs that estimate or debit after usage still leave room for a separate customer-facing signed reservation step.
Quote payload, options, route identity, rate card, expiry, signature, reservation
Evaluate a signed generation quote as seven linked fields that fail differently. The payload must identify the generation request. Model options must be hashed or otherwise bound so a later edit cannot reuse the old charge. Route identity must name the selected provider path for the fixed public model. Rate-card version must pin which normalized wholesale/retail inputs produced the credit charge. Expiry must bound how long the signature remains acceptable. Signature verification must reject tampering. Reservation must move credits only after those checks pass.
OfflineCreator’s hub copy and provider-routing notes describe that sequence in operational language: match eligible routes, compare healthy routes near the lowest eligible cost, sign the selection for five minutes, reserve the signed credit charge, then generate. After lock-in, a safe alternate route may run only inside the locked customer envelope. Studio, REST API, CLI, and MCP are documented to share the same signed quote flow.
Do not confuse this integrity lifecycle with plan menus or payment capture. The quote decides which credit amount is reserved for one generation request under one option set. It does not authorize a subscription, invent wholesale savings, or guarantee that every managed route in internal docs is already live for anonymous production traffic.
- Quote payload
- Bound request envelopeRecords the selected route, options, rate card, credit charge, and expiry before credits move.
- Model options
- Material settings are part of the lockDuration, resolution, and related options define compatibility and require a fresh quote when changed.
- Route identity
- Selected provider pathThe public model stays fixed while the signed selection names the configured route chosen at quote time.
- Rate-card version
- Pinned pricing inputsThe quote carries the rate-card identity used to compute the customer credit charge for that selection.
- Expiry and signature
- Time-bounded integrityDocumented signing lasts five minutes; reservation should accept only a still-valid signed envelope.
- Reservation
- Credits move after approvalStudio signs and reserves the customer quote before submission; failover cannot raise the approved charge.
Where to go next without leaving quote integrity
If you need the broad Kayak-style routing overview, start at the parent AI Router hub. Stay on this child page when the question is specifically whether the quote payload, signature, expiry, and reservation form a trustworthy lifecycle before credits move.
If your next concern is what happens after an ambiguous provider failure, continue to prevent duplicate AI generation jobs. If you are evaluating how eligible routes are cost-ranked before a quote is issued, continue to AI generation cost routing. If you need how wholesale cards are normalized into comparable request units, continue to normalize AI provider rate cards. This page does not own subscription pricing or payment authorization.
Canonical ownership and evidence boundary
This URL owns quote integrity and lifecycle for the query “signed ai generation quotes.” The /ai-router hub owns the broad AI generation router overview. OfflineCreator’s x402 rail can price a pay-as-you-go challenge from the same locked quote; payment mechanics live on /x402 rather than this page.
Supported product statements here are limited to OfflineCreator’s documented signed-quote flow, provider-routing notes verified against first-party sources, and the live cloud provider disclosure. Supported external statements are limited to fal’s published Model APIs pricing docs and OpenRouter’s FAQ on post-request credit deduction. This draft does not assert live production availability of every managed multi-provider route, does not publish wholesale examples as customer price guarantees, and does not invent privacy, retention, benchmark, or outcome claims.