Skip to main content
This page lists the messages the LLM Gateway returns when it refuses a call, and how to fix each one. When the gateway does not send a call to a provider, it answers in the caller’s own format (Anthropic, OpenAI or Gemini), so your coding tool or app shows the message as an error. The call costs nothing, and it appears in Logs with the reason in Status and in its Gateway decisions. In Xpander Chat, a run refused this way ends with a card titled xpander did not send this request, followed by the same message and what to do.

Your key

The model

Provider keys and endpoints

On xpander cloud, saving an endpoint at a private, loopback or cloud metadata address fails at once with Model endpoints are called at public addresses here, so this endpoint was not saved.

Budgets, credits and rate limits

Your own Claude plan

The gateway itself

When the gateway is unavailable

Agents call models only through the LLM Gateway. When it cannot be reached for 30 seconds or more:
  • Xpander Chat shows a banner: AI gateway is unavailable. Agents can’t run right now. We’ll reconnect automatically.
  • A new run or chat message is refused at once, and a run in progress stops at its next model call, with the card This run stopped because the AI gateway is unavailable. Retry once it is back.
  • Calls from coding tools and SDKs answer 503 with a Retry-After header.
In the meantime, nothing is sent to a provider any other way. The gateway reconnects on its own, usually within a minute, and the banner clears.

When the provider refuses

When the call reached the provider and the provider refused it (for example, an invalid request or a model that does not exist), the provider’s own error comes back unchanged. In Xpander Chat the card is titled The model provider rejected this request.