#29961 How should an independent OpenAI-compatible gateway be represented in model_prices_and_context_window.json?
Hi LiteLLM maintainers,
I would like to add pricing metadata for Starveri API, an independent OpenAI-compatible GPT/Codex API gateway with public model metadata and a direct prepaid-credit buyer path.
Before opening a PR, I wanted to ask which provider representation you prefer for independent OpenAI-compatible gateways. I checked model_prices_and_context_window.json and did not find current entries using litellm_provider: custom_openai, so I do not want to submit a shape that does not fit your conventions.
Public source links: - Pricing / buyer page: https://api.starveri.net/credits - Public model metadata: https://api.starveri.net/models - Docs: https://api.starveri.net/docs - OpenAPI: https://api.starveri.net/openapi.yaml - LLM discovery: https://api.starveri.net/llms.txt
Canonical public models: - gpt-5.1-codex - gpt-5.3-codex-spark - gpt-5.3-codex - gpt-5.4 - gpt-5.4-mini - gpt-5.5
The public /models endpoint exposes USD per 1M token prices for cached input, input, and output. It also exposes non-billable global model-spec metadata.
Would you prefer: 1. Dedicated model keys such as starveri/gpt-5.5 with a Starveri-specific provider name, 2. A custom OpenAI-compatible pro…