Troubleshoot API and MCP connections
Distinguish API keys from OAuth, resolve permissions and upload issues, and recover quotes or uncertain paid requests without bypassing safeguards.
On this page
Use the right connection and credential
| Integration | Address | Authentication |
|---|---|---|
| Public API | https://api.animgen.com/v1 |
Appropriately scoped Bearer API key |
| Official remote MCP | https://api.animgen.com/mcp |
OAuth, through a compatible Streamable HTTP client |
| Tool manifest | https://animgen.com/mcp/tools.json |
Public documentation; not an MCP connection |
The MCP service is live in public beta. A browser opening the MCP URL without OAuth can receive an authentication response; it is not a normal HTML page. That alone is not evidence that the service is down.
Do not substitute an API key for MCP OAuth, reuse a website login token as an API key, or append an invented /sse path. Follow MCP client setup.
Login succeeds but tools fail
Check that the signed-in AnimGen account is verified, developer access is not paused, and the required scopes were granted. Then check the credit balance for any cost-bearing generation.
A revoked grant, missing scope, or incompatible client authorization flow must be fixed independently of credit balance. Reconnect through the official flow if needed; do not disable PKCE or weaken redirect validation to bypass a client error.
Use list_models as the first read-only check. Success verifies that connection and read permission, not upload capability, generation approval, or complete end-to-end output quality.
Upload or download is incomplete
The remote server cannot read a local path. After prepare_image_upload, a separate approved client capability must send the actual bytes, and complete_image_upload must return a usable file ID.
Likewise, download_asset returns metadata and a temporary URL, not a file already saved on your computer. Download the bytes without forwarding API/OAuth credentials. If your client lacks these capabilities, state the limitation and use an approved supported alternative.
Quote and spending refusals
| Code | Next action |
|---|---|
SPEND_CONFIRMATION_REQUIRED |
Obtain concrete approval and supply the required guard |
QUOTE_EXPIRED |
Re-quote and review the updated amount |
QUOTE_MISMATCH / QUOTE_CHANGED |
Reconcile changed parameters or price, then seek approval |
QUOTE_ALREADY_USED |
Recover the original operation, not a new use of that quote |
CREDIT_LIMIT_EXCEEDED |
Stop; reduce scope or ask for a different approved cap |
INSUFFICIENT_CREDITS |
Explain the balance issue; do not auto-purchase |
quote_id and max_credits are MCP tool arguments beside request. They are not Public API body fields. A per-operation cap is not a total session budget. See spending safeguards.
Recover an uncertain create safely
Retain the same request, idempotency key, account, and credential identity: API key ID for API, OAuth client for MCP. Do not switch keys or clients and assume deduplication follows you.
Poll a known task before retrying creation. Respect retryability and the API's Retry-After when present; MCP structured errors are not guaranteed to carry that HTTP header. Bound retries and local waiting.
A local timeout does not cancel the remote task. Terminal failure can contain partial outputs and charges. For support, privately provide request/task IDs, timestamps, error code, client type, and failing stage, without secrets or signed links.
Was this page helpful?
No search queries, code, or free text are collected. This switch controls documentation interactions only; general site analytics follow the privacy policy. Privacy policy