[Bug]: [API Platform] Unable to generate API Keys when no gateways are available for the Org

Please select the area the issue is related to

Area/Management (Management API or Management Portal UI), Area/Other (Anything else which does not match above categories)

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)

Description

$subject

time=2026-06-25T21:30:09.212+05:30 level=WARN source=service/llm_apikey.go:234 msg="No gateways found for organization" organizationId=99089a17-72e0-4dd8-a2f4-c8dfbb085295
[GIN] 2026/06/25 - 21:30:09 | 503 |    3.777625ms |             ::1 | POST     "/api/v0.9/llm-providers/wso2-openaiprovider/api-keys?organizationId=99089a17-72e0-4dd8-a2f4-c8dfbb085295"

Steps to Reproduce

Login to AI workspace for the first time
Create a LLM provider and then create the LLM Proxy
Try to generate an API Key for the LLM Proxy

Severity Level of the Issue

Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)

Environment Details (with versions)

No response

Start with service/llm_apikey.go around line 234 and reproduce the POST /api/v0.9/llm-providers/wso2-openaiprovider/api-keys request after creating the provider and LLM Proxy. Trace how the missing gateway is handled and confirm the intended behavior for API-key generation when no gateways are available. Done means the endpoint handles this first-time workspace flow as intended instead of unexpectedly returning 503.