Skip to content

Support Requesty as a BYOK provider #1383

Description

@Thibaultjaigu

Summary

Add Requesty — an OpenAI-compatible LLM gateway — as a first-class BYOK provider, alongside the existing OpenRouter provider.

Motivation

Requesty exposes one OpenAI-compatible API across many models, using the same provider/model naming as OpenRouter (base URL https://router.requesty.ai/v1, auth Authorization: Bearer $REQUESTY_API_KEY, model listing at /v1/models). Users who want to route their code-review models through Requesty currently can't select it.

Proposed change

Wire Requesty through the existing BYOKProvider system on the generic OpenAI-compatible path (the same path NOVITA uses), with its own fixed base URL and /v1/models listing — NOT through OpenRouter's SDK-specific provider-routing / reasoning namespaces (which Requesty does not support):

  • BYOKProvider enum + adapter selection + display label (packages/kodus-common)
  • ProviderService provider catalog entry
  • byok-to-vercel adapter (createOpenAICompatible at the Requesty base URL)
  • agent-loop providerOptions namespace (openaiCompatible)
  • get-models-by-provider model listing (getRequestyModels)
  • env: API_REQUESTY_API_KEY

env: REQUESTY_API_KEY / API_REQUESTY_API_KEY.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions