Manage API keys, quotas and AI usage
Use the CodingRouter API platform to manage API keys, token groups, quotas and model usage. Keep service access separate from Connect’s local tool configuration.
Organize access by application or workflow
Use meaningful token names so that you can recognize the application or coding tool using each key. Check the available group and model permissions when selecting a token. The desktop tool shows this context during setup, while the existing API platform remains the place to manage your account.
Check quota and expiry before connecting
A token must be available for the model and workflow you select. Review its quota and expiry instead of assuming access is unlimited or permanent. In Connect, creating a token requires quota confirmation, and unlimited quota or permanent validity must be chosen explicitly.
Review account balance and usage in the platform
Use the API platform for the current balance, usage records and account operations. A successful installation or saved configuration is not evidence that a model call succeeded or that usage is free. Check current model pricing before making requests; this website does not publish a second price list that could become outdated.
Troubleshoot access without sharing credentials
For an access problem, check whether the token is available, its group permits the model, its quota is sufficient and the client uses the intended configuration. Do not paste a key, full configuration or backup into a public issue. If local settings are the problem, use Connect’s configuration preview and backup restoration instead of repeatedly replacing keys.
Multi-model AI API access with CodingRouter
Connect your applications and AI coding workflows to CodingRouter APIs. Manage model access and usage in the API platform; use Connect when you want a desktop tool to configure supported coding clients.
Manage API keys, quotas and AI usage
Use the CodingRouter API platform to manage API keys, token groups, quotas and model usage. Keep service access separate from Connect’s local tool configuration.