Domain Routing
Why there are multiple addresses
The current Codebyby rollout separates several public entry points so the docs site, main site, and live API relay do not share the same public route responsibilities.
- Main site domain: login, dashboard, and product entry
- Docs domain: onboarding, FAQ, privacy policy, terms, and contact pages
- API relay endpoint: actual request traffic, provided by the operator or deployment owner
Where to get the correct address
Always use the address published by the current deployment. Typical sources are:
- Connection information shown in the dashboard
- Onboarding material provided by the operator
- Public guidance on this docs site
Do not assume the upstream provider host, and do not treat the docs domain as the API endpoint.
Typical responsibility split
A common deployment usually looks like this:
- Main site: account login, pricing, and key management
- Docs site: setup guides and public legal pages
- API relay: the endpoint your client actually calls
They may share the same brand, but their domains and paths usually serve different purposes.
What to do when routing changes
If the operator changes the domain, path prefix, or gateway policy, use this order:
- Update the base URL in environment variables or client config.
- Verify the new address with a minimal request.
- Switch production traffic only after validation.
- Keep the previous config briefly for observation and rollback.
Common beginner mistakes
- Using the docs domain as the API endpoint
- Copying an upstream example without replacing the relay address
- Updating only the host but not the path prefix
- Keeping an old base URL in local environment variables after a rotation