Built for developer tools
Offer model choice without turning your product into a secret manager
Developer tools can expose a reviewed model shortlist through one gateway integration, while keeping protocol and capability differences explicit. Separate scoped keys make environments and product surfaces attributable without distributing provider credentials.
Last reviewed 2026-08-15 · Editorial review: KeepRouter Editorial
Build a narrow catalog, not a model dropdown dump
Users value model choice when the choices work in the product. Start with the tool's actual client protocol, streaming parser, tool schema, context needs, and maximum acceptable cost. Publish only IDs you have run through those paths, even if the gateway catalog is broader.
Product architecture
Keep the KeepRouter key on your server. Map user-visible labels to canonical model IDs in a reviewed configuration file. Create separate keys for production, staging, background jobs, and internal evaluation. Apply a model allowlist and spend control to each key so a UI change cannot silently unlock unrelated models.
Make compatibility visible
OpenAI-compatible and Anthropic-compatible refer to request shapes, not identical model behavior. A developer tool should document which path it uses, whether tools and images are enabled, how streams end, and what happens when a configured ID is unavailable. Link each option to its live model page instead of copying a price snapshot.
A rollout that can be reversed
Release a candidate to internal accounts, then a small product cohort, then the public selector. Record model ID, application version, request status, tokens, cost, and task outcome. Keep the previous ID as an evaluated rollback, but do not replay side-effecting tool calls automatically.
Trust surfaces for your users
Explain that the tool uses a routing intermediary and link to data handling. If you pass user content, define your own retention and consent policy; KeepRouter's request log boundary does not replace your obligations. Expose an error reference and a route status link rather than promising uninterrupted upstream availability.
Frequently asked questions
Should a developer tool expose the full catalog?
Usually no. Expose a tested shortlist that matches the tool's protocol and workflow.
Where should the gateway key live?
Keep it server-side. Do not ship a reusable secret in a browser or desktop bundle.
Can we attribute usage by product surface?
Use separate scoped keys for environments, services, or surfaces, then combine gateway records with your own product events.
How should we publish prices?
Link to the live catalog or consume its public data; avoid copying a static price table into product copy.