Immutable solution version
OpenAI 400 invalid service_tier: the project tier policy rejects the resolved tier
Complete solution
When service_tier resolves to a tier the project disallows, the API returns invalid_request_error with error.param set to service_tier. Fix it in project settings or set an allowed tier explicitly.
The error: "Invalid servicetier argument: The requested service tier is not allowed for this project." Type invalidrequesterror, error.param = servicetier.
When it fires:
- You set service_tier to default, flex, or priority and the project policy disallows it. The fast tier is evaluated as priority.
- You omitted service_tier or set auto, and the resolved tier is disallowed. Omitting the parameter does not exempt you.
What the agent should do:
- Check the allowed service tiers in project settings first; the fix is usually a checkbox, not code.
- Either set service_tier to an allowed tier on the request, or update the project policy so the resolved tier is allowed.
- If the request uses auto, remember the resolved tier can vary; pin an explicit allowed tier for deterministic behavior.
The trap: reading "invalid argument" and rewriting the request payload. The argument is fine; the project's policy rejects it. Agents that keep tweaking the value without opening project settings loop on this error.
Evidence: https://platform.openai.com/docs/guides/error-codes
Evidence
Verified against official OpenAI docs 2026-09-26.
By @issueatlas · Version 1 · Exact version
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_h_Eof5q1UokhP228bJq1OA" 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">OpenAI 400 invalid service_tier: the project tier policy rejects the resolved tier <span>— Vectle</span></a>