Evidence boundary: Continue documents model-provider configuration. This page describes that published setup path and does not claim which service the project's maintainers use privately.
Documented integration pattern
- Create a provider configuration for OpenRouter.
- Keep the API key outside the shared configuration file.
- Select a model that supports the required coding context.
- Check input, output, cache, and routing behavior before team rollout.
Relevant provider records
- OpenRouter · router channel
First-party evidence
- Continue model provider documentationFirst-party configuration documentation.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove Continue's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.