
Check a proposed Imagild workload against current model prices and the balance information available through your authorized account workflow, but treat the server's reservation as authoritative. A client-side “enough points” estimate can become stale when another website or API task spends from the same wallet.
This is a preflight design for your application, not a new balance or price-override endpoint. Use the model hub for current rates and the API console for accepted request fields.
Key Takeaways
- Calculate the proposed task before showing a spending confirmation.
- Separate active membership from available points and planned task cost.
- Handle a reservation rejection without automatically increasing the budget or changing operation identity.
Build a quote from exact settings
A text-only 2K image currently needs 15 points. An eight-second 768P video with enhancement disabled needs 120. A 2K source image plus that video therefore needs 135 generation points if both are newly created.
Use actual selected settings rather than a default displayed elsewhere in the interface. The same account can use points in the website and API, so a different tab's work can matter.
A small local estimator can help catch incomplete budgets:
function plannedPoints(items) {
if (!Array.isArray(items)) throw new TypeError("Expected an item array");
const imageRates = { "1K": 10, "2K": 15, "4K": 20 };
const videoRates = { "768P": 15, "2K": 30 };
let total = 0;
for (const item of items) {
if (!item || typeof item !== "object" || Array.isArray(item) ||
typeof item.resolution !== "string") {
throw new Error("Unsupported budget item");
}
let cost;
if (item.kind === "image" && Object.hasOwn(imageRates, item.resolution)) {
cost = imageRates[item.resolution];
} else if (item.kind === "video" &&
Number.isInteger(item.seconds) &&
item.seconds >= 4 && item.seconds <= 15 &&
Object.hasOwn(videoRates, item.resolution) &&
typeof item.context_ir === "boolean") {
cost = item.seconds * videoRates[item.resolution] +
(item.context_ir ? 5 : 0);
} else {
throw new Error("Unsupported budget item");
}
total += cost;
if (!Number.isSafeInteger(total) || total < 0) {
throw new Error("Budget exceeds safe integer range");
}
}
return total;
}
Require string resolution values and test only own properties, as documented by MDN Object.hasOwn. Inputs such as constructor, __proto__ or ["2K"] must be rejected rather than converted into a quote. This example contains the rates checked on 28 October 2026. In production, validate model availability and obtain current pricing before quoting. These local kind items describe your planning model; do not send a kind field to the generation endpoints.
Understand the concurrent-balance race
Suppose your account shows 150 available points. Two independent application sessions each plan a 120-point video. Both can pass a local comparison against the old snapshot, although the wallet cannot fund both reservations simultaneously.
Do not solve this by subtracting 240 from a browser variable and claiming both tasks are accepted. Coordinate your own application submissions, then respect the provider's authoritative result. Website use or another client can still change availability outside your local coordinator.
Runware's pricing reference illustrates configuration-based generation budgeting. Its balance-management features are not additional Imagild API endpoints; this contract does not provide GET /balance.
Separate the three preflight questions
First, does the account currently have active membership for API access? Second, is the chosen model and parameter combination supported? Third, does the current available balance appear sufficient for the complete approved plan?
A points purchase does not answer the first question. A valid duration does not answer the third. A budget buffer can reduce surprises, but it is an application policy rather than a guarantee that reservation will succeed.
Keep the exact quoted plan beside the confirmation. If the user changes resolution, adds a source generation or allows another shot, show the changed total before submission.
Recover from rejection without expanding spending
If the server rejects a reservation, preserve the safe error code and original operation record. Do not silently switch to a cheaper model, shorten the video or recharge the account. Those are separate user decisions.
If a submission's outcome is ambiguous, retain the original idempotency key and unchanged parameters. A reservation rejection and an unknown result require different handling; the failed-job guide helps organize that diagnosis.
Test the estimator with supported settings, invalid durations and two simultaneous sessions sharing a stale balance snapshot. Confirm that the second session handles a server rejection clearly. Use the points planning guide to explain the final spending decision without inventing a prepaid guarantee.
Related tasks
- What Should You Check Before Retrying a Failed Image or Video Job?
- Imagild Points, Resolution and Jobs: Plan a Creation Before You Spend
Sources and scope
- Imagild API console: Current active-member access, generation contract and per-task usage fields, independently cross-checked in lib/relay and claims.json dated 2026-10-28.
- Imagild model hub: Current image 10/15/20-point tiers, H3 duration/resolution rates and five-point enhancement option; not a quality or comparative availability benchmark.
- Runware Pricing: General distinction between configuration-based generation pricing, per-request cost and account payment management. Runware-specific fields, features and policies are not attributed to Imagild.
- MDN Object.hasOwn: Own-property checks exclude inherited dictionary properties.
Product instructions were checked against the current Imagild API contract and the public model catalog. Code, budgets and acceptance checks are illustrative; this article does not claim a new paid generation test, an uptime measurement, a search-volume study or a ranking of AI citations.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Original Imagild product screenshot captured on 28 October 2026; model availability and prices may change. This image is not an API response or a performance benchmark.