
An Imagild API request must pass three separate checks: the key must be valid, the account must have active membership, and a generation must have enough available points. Buying points does not activate API membership, and a key that was created earlier does not bypass a later membership expiry. Start with the API console, then check the account's access and balance independently.
Key Takeaways
- Membership grants current API eligibility; purchased points fund successful generation.
- Key validity is a separate condition, so a 401 and a membership-related 403 need different fixes.
- A read-only catalog request can check access without submitting a paid media task.
Diagnose the gate that actually failed
Imagine an account with 500 points and an unexpired key. If its membership has ended, adding another points pack changes the balance but does not resolve API eligibility. Conversely, an eligible member with a good key can read the catalog while lacking the budget for the next video.
| Condition | What it establishes | What it does not establish |
|---|---|---|
| Valid, unexpired, unrevoked key | The presented secret identifies an accepted API credential | Current membership or enough generation points |
| Active membership | The account currently qualifies for API access | A valid key or unlimited generation |
| Available points | A budget can be reserved for an accepted paid task | API eligibility without membership |
| A completed task | Generation reached a successful task outcome | Permanent anonymous access to its file |
Treat this table as an access decision, not a product bundle comparison. Legacy website subscriptions can retain their own terms; use the current console rather than inferring eligibility from a remembered checkout name.
Make a non-generation access check first
Use the authenticated model catalog to distinguish basic access problems from generation parameters:
curl --silent --show-error --dump-header access.headers \
--output access.json --write-out '%{http_code}\n' \
'https://imagild.com/api/relay/v1/models' \
-H "Authorization: Bearer $IMAGILD_API_KEY"
Do not paste the key into a browser address. Inspect the HTTP status and the JSON error.code together. An invalid, expired, or revoked credential returns 401. A valid credential for an account without active membership can return 403 with RELAY_MEMBERSHIP_REQUIRED. Rate limiting and temporary unavailability are separate possibilities, so avoid a blanket “all failures mean expired membership” message.
The OWASP endpoint-authorization guidance supports checking authorization for each protected operation. Imagild applies membership checks to reads and content downloads as well as generation submissions.
Calculate the next operation independently
The model hub lists image costs of 10 points at 1K, 15 at 2K, and 20 at 4K for each public image model. A four-second 768P H3 task uses 60 points with context_ir disabled. A separately generated reference image is another task.
For an account holding 50 available points, a 1K image fits that point budget, while the four-second video does not. This arithmetic says nothing about whether the account has API membership. Likewise, welcome points are not a free API-access entitlement.
Use the existing points explanation to separate the wallet from the credential. The advantage of a shared wallet is that the website and API draw on one understandable account balance, not that every feature is unlocked by every purchase.
Build useful application messages
Keep a small diagnostic record containing the HTTP status, sanitized error code, and request_id when returned. Present different next actions:
- For 401, check the secret selected by the application's environment, its expiry, and revocation.
- For the membership-specific 403, check the account's current membership in the console.
- For a point-budget problem, inspect the requested operation's cost and any existing reservations.
- For 429, reduce requests and respect the response's retry guidance.
Do not “test the fix” by repeatedly posting new generations. Confirm access with GET /models, then let the user approve an appropriately budgeted operation. Review failed-job next actions when a task already exists: account access, task outcome, and point settlement remain distinct questions.
Related tasks
- How do Imagild points work for photos and video?
- What Should You Check Before Retrying a Failed Image or Video Job?
Sources and scope
- Imagild API console and integration guide: Product entry point and current API access, credential and task integration instructions; detailed facts also cross-checked against the 2026-10-28 repository contract.
- Imagild model hub: Current public media model choices and resolution-based point prices; not evidence of model equivalence, pixel quality or measured uptime.
- OWASP REST Security Cheat Sheet: General REST security principles: endpoint authorization, secure handling of credentials, input validation and response content-type checks. Does not define Imagild product behavior.
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.