Frequently Asked Questions
Have questions? Reach out anytime.
Contact UsIs there account suspension risk?
No. Requests are routed through an encrypted channel to upstream models and consume our enterprise API quota, fully separated from your personal account.
Which models are supported?
Codex-related models are supported first. More model groups can be added as channels become stable. Availability, context length, rate limits, and pricing are subject to the console.
How can pricing be lower?
Full-access pricing reflects channel cost, quota structure, procurement, and routing strategy. It is not a simple resale of official retail pricing. Final pricing should be confirmed in the console or through commercial communication for project-level cost planning.
Will quota expire?
Balance, promotional credit, bonus quota, and enterprise billing terms may follow different rules. For production use, rely on the console billing page, quota notes, and service terms, and configure budget alerts.
How is it different from the official API?
Official APIs are provided directly by model vendors. StringRoute provides a unified endpoint, grouped pricing, aggregated billing, key management, and integration support. Model capability and limits still depend on upstream models and channels.
Will requests be trained on or resold?
StringRoute is built around transit and billing, not selling request data. Request-body handling, retention, and troubleshooting scope follow the privacy policy and console settings.
How do I integrate an existing project?
In most cases, replace the Base URL, API Key, and model ID, while keeping OpenAI-compatible SDKs or request formats. See the integration docs for parameters, examples, and scripts.