specs: add Requesty to the model catalog#19
Open
Thibaultjaigu wants to merge 1 commit into
Open
Conversation
Requesty (https://requesty.ai) is an OpenAI-compatible gateway that exposes a standard /v1/models endpoint. This adds it to the catalog the same way OpenRouter is wired: - model_catalog.py: requesty floor list in STATIC_MODEL_CATALOG + its upstream /v1/models URL in _PROVIDER_ENDPOINTS (live-merge uses Bearer auth, which Requesty accepts) - tests/test_model_catalog.py: floor + live-merge tests for requesty - docs/configuration.md: router.requesty.ai -> requesty in the provider_map example Verified: tests/test_model_catalog.py passes (15 tests incl. 2 new); ruff and mypy clean on touched files. Floor model IDs limited to slugs verified to route on Requesty.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Requesty to the model catalog, mirroring how OpenRouter is wired. Requesty is an OpenAI-compatible gateway that exposes a standard
/v1/modelsendpoint, so it slots into both the static floor and the live-merge path.src/ccproxy/specs/model_catalog.py:requestyfloor list inSTATIC_MODEL_CATALOG"requesty": "https://router.requesty.ai/v1/models"in_PROVIDER_ENDPOINTS(the live-merge fetch usesAuthorization: Bearer, which Requesty accepts)tests/test_model_catalog.py: a floor test and a live-merge test forrequesty(mirroring the anthropic ones)docs/configuration.md:router.requesty.ai -> requestyin theprovider_mapexampleFloor model IDs are limited to slugs I verified actually route on Requesty.
Tested
uv run pytest tests/test_model_catalog.py— 15 passed (incl. 2 new)uv run pytest tests/ -k "catalog or models or config or spec"— 260 passeduv run ruff checkanduv run mypyon the touched module — cleanGET https://router.requesty.ai/v1/modelsreturns an OpenAI-shaped{object: list, data: [...]}payload.Note: I couldn't get a clean run of the entire suite locally — an unrelated test elsewhere hangs at ~59% on my machine (looks like an e2e/namespace test needing network/WireGuard), well outside this change. The catalog area and its neighbors are fully green. Happy to adjust if CI surfaces anything.
Disclosure
I work at Requesty. This mirrors the existing OpenRouter catalog entry. Happy to adjust naming/placement or close if it's not a fit.