- Migration
Moving from ngawi-proxy
Switch your client's base URL and nothing else changes: the key, the balance, and the request shape all stay the same. The previous endpoint continues to serve traffic while you make the move.
New to routr? Use the application quickstart instead. This guide is for existing ngawi-proxy accounts and integrations.
Keep your key
Your sk-user- key and balance carry over 1:1. No new account, no re-registration.
Change the base URL
Point your client at the routr.cloud endpoint. The request shape is unchanged.
Watch the ledger
Balance, limits, and usage are visible in your workspace from the first request.
- Base URL
The only change
Swap the base URL. Everything else is identical: the key, the model id, the request body, and the response shape.
# before
https://api.ngawi-proxy.cloud/v1
# after
https://api.routr.cloud/v1Model names
Models you already call are reachable under their existing names. A few names that only existed in the previous catalog are no longer offered. The Model catalog lists what is served today, and the changelog records what changed.
During the transition
Both endpoints run side by side, so traffic that still points at api.ngawi-proxy.cloud keeps flowing while you verify the routr endpoint end-to-end before you commit.
Verify your migration
Open your workspace to confirm your balance. After sending a request through the new endpoint, inspect its outcome and charge in Usage.