Migrating to Cloakray

Moving to Cloakray is mostly a configuration change. Your SDK, prompts and request shapes stay the same; the base URL, the key and the model IDs change. What does change is how you pay: instead of a card on file, you fund a balance with crypto before you send traffic.

• From OpenAI or Anthropic — keep the official SDKs, and gain every other lab's models on the same key
• From OpenRouter — same OpenAI-compatible format, model IDs without the provider prefix
• From the Vercel AI Gateway — repoint the AI SDK's gateway provider or its OpenAI-compatible endpoint

A safe rollout

1. Top up the balance with crypto and wait for the payment to confirm. A small amount is enough to test with.
2. Create a key in a separate project, such as migration-test, so test traffic is easy to find.
3. Change the base URL and key in one environment, and map your model IDs to the catalogue.
4. Run your test suite and compare outputs, latency and cost in the logs.
5. Add enough credit for production, then move it over one service at a time.

There is no automatic top-up with crypto, so size the production top-up to a few days of the spend you saw in testing, and keep an eye on the balance in analytics.

Keep the old configuration behind an environment variable until you're confident: switching back is the same two settings.