feat(gateways): add generic Corporate AI gateway placeholder#13
Merged
Conversation
Adds a non-vendor gateway entry at the top of the catalog so users without a specific gateway in mind see something neutral first. baseUrl uses <your-org> so the placeholder warning fires on the un-substituted template. - id: corporate - baseUrl: https://gateway.<your-org>.com - endpoints: openai /v1, anthropic /v1/messages - auth: Authorization Bearer, env: GATEWAY_API_KEY - notes: 'Generic placeholder for any OpenAI-/Anthropic-compatible gateway. Set base URL when applying.' Catalog now has 11 rows (was 10). Vendor entries (TrueFoundry, LiteLLM, Cloudflare, etc.) stay intact for users on a specific platform.
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.
Summary
Adds a non-vendor gateway entry to the catalog so users without a specific platform in mind see something neutral first. The wizard card shows
https://gateway.<your-org>.comwith a placeholder warning, and applying requires the user to fill in their own hostname.New entry
{ "id": "corporate", "label": "Corporate AI gateway", "baseUrl": "https://gateway.<your-org>.com", "selfHostedHint": "Replace <your-org> with your hostname. Often exposed at /v1/chat/completions (OpenAI) and /v1/messages (Anthropic).", "endpoints": { "openai": "/v1", "anthropic": "/v1/messages" }, "auth": { "header": "Authorization", "scheme": "Bearer", "envVar": "GATEWAY_API_KEY" }, "modelIdFormat": "<model>", "nativeProviders": ["anthropic", "openai"], "notes": "Generic placeholder for any OpenAI-/Anthropic-compatible gateway." }Catalog now has 11 rows (was 10). Vendor entries (TrueFoundry, LiteLLM, Cloudflare, etc.) stay intact for users on a specific platform.
Verification
npm run typecheck && npm run lint && npm run build✓node scripts/gen-catalog.mjsregeneratedcatalog.generated.tsfill in <your-org>warningWhy not just genericize everything
The vendor entries are real — they encode each gateway's actual auth shape (TrueFoundry accepts both
x-api-keyandBearer; Cloudflare needs an account_id in the path). Removing them would leave enterprise users unable to point Hoist at their actual gateway.