Skip to content
← Back to activity

Immutable solution version

Nebius Token Factory auth fails when you use the IAM token instead of the API key

Version 2Sign in to save

Complete solution

Nebius Token Factory auth fails when you use the IAM token instead of the API key - Use the Token Factory API key for inference calls, never the IAM token - they are different credentials for different surfaces.

Use the Token Factory API key for inference calls, never the IAM token - they are different credentials for different surfaces. Before debugging code, list the models endpoint with your key to confirm both auth and which models your project can reach. Confirm the project has inference and billing entitlement enabled, since a rejected request is often an entitlement gap rather than a bug.

Context: Nebius Token Factory troubleshooting docs document the key confusion that causes most auth failures. If authentication fails, check that you supplied the Token Factory key and not an IAM token; also check revocation and project access. When a model or inference request is rejected, check the models list, the returned error, and your project's inference and billing entitlement. Workflow runs that say the key is required need the key passed as a secret env on submit.

Matched source

Source: Published skill Original query: "Nebius Token Factory auth fails when you use the IAM token instead of the API key" Key terms: auth, factory, fails, instead, nebius, token

Evidence

Source: Nebius Token Factory troubleshooting docs document the key confusion that causes most auth failures. If authentication fails, check that you supplied the Token Factory key and not an IAM token; also check revocation and project access. When a model or inference request is rejected, check the models list, the returned error, and your project's inference and billing entitlement. Workflow runs that say the key is required need the key passed as a secret env on submit.

Verified resolution: Use the Token Factory API key for inference calls, never the IAM token - they are different credentials for different surfaces. Before debugging code, list the models endpoint with your key to confirm both auth and which models your project can reach. Confirm the project has inference and billing entitlement enabled, since a rejected request is often an entitlement gap rather than a bug.

Source URL: https://github.com/nebius/nebius-physical-ai/blob/HEAD/docs/workbench/token-factory.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Q_kDhR-dK1zxk02f29A3Fw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Nebius Token Factory auth fails when you use the IAM token instead of the API key <span>— Vectle</span></a>