Migrating your credits from nexos.ai to Hostinger AI Router credits

See when your nexos.ai credits migrate and how to update your API setup.

Updated 5 days ago

Hostinger AI Router is Hostinger’s own AI gateway. It gives you access to leading large language models through a single API key and a single credit balance, managed directly in Hostinger dashboard.

All existing AI credits are moving to Hostinger AI Router. Your balance is carried over in full, but your API key and base URL change, so any script, agent, or workflow you run will need a short update. This article explains exactly what changes, when it happens for you, and what you need to do.

What changes

Three things change when your account moves to Hostinger AI Router.

What Before After
Base URL https://api.nexos.ai/v1 https://router.hostinger.com/v1
API key Your previous key A new Hostinger key starting with sk-hstgr-
Model names Your previous model IDs Shorter, simpler model names
Credit balance Your current balance The same value, converted at 1 credit to 100 credits

What happens to your credit balance

Your balance is converted at a rate of 1 credit to 100 credits. This is a change in how credits are counted, not a change in value. A balance of 5 credits becomes 500 credits, and it buys exactly the same amount of AI usage as before.

Because the unit is smaller, the credit cost of each model is also 100 times larger than the number you saw previously. A model that cost 3.3 credits per million input tokens now costs 330 credits per million input tokens. Nothing has become more expensive.

Your converted balance is always visible in Hostinger dashboard → AI Router, together with your usage for the current period.

When the migration happens for you

The migration happens at different times depending on how you use your credits. Find the case that matches your account.

If you still have credits and use them regularly

Nothing breaks. You can keep spending your existing balance exactly as you do today, with your current API key and base URL.

While you still have a balance, the top-up button is hidden. Once your balance runs out, the top-up button returns and your next purchase will be Hostinger credits. At that point you will receive a new API key and you will need to update your setup as described below.

If you have credits but rarely use them

Your account will be migrated automatically. Before this happens you will receive an email, and you will see a banner and a notice in Hostinger dashboard.

At migration your balance is converted at 1 credit to 100 credits and a new API key is issued. Your previous key stops working at that moment, so your requests will fail until you update your setup.

If you are a new customer

You already have Hostinger credits and a Hostinger API key. There is nothing to migrate.

Switching before you are migrated

You do not have to wait. Once you have spent your existing nexos.ai credits balance, you can buy Hostinger credits straight away at AI Router in Hostinger dashboard. You will be able to create your new API key and the base URL will appear in Hostinger dashboard immediately after the purchase.

The same balance also works across other Hostinger AI products, so a single top-up covers everything you run.

How to update your setup

Once you have Hostinger credits, update both values everywhere you use AI. Changing only one of them will not work.

Step 1 – Copy your new details

  1. Log in to Hostinger dashboard
  2. Open AI Router
  3. Copy your API key from the API key section.
  4. Note the base URL: https://router.hostinger.com/v1
  5. Find a new model slug (you can find it on the Models page).

Step 2 – Replace them in your code

If you use the OpenAI or Anthropic SDK, change the base URL and the key. No other code changes are required.

from openai import OpenAI

client = OpenAI(
    api_key="YOUR_KEY_HERE",
    base_url="https://router.hostinger.com/v1"
)

Step 3 – Replace them in your applications

Update the same two values in every place you use AI, including automation workflows, coding tools, and any application running on your VPS.

Step 4 – Test a request

Run a single request to confirm the connection works. Your usage appears in Hostinger dashboard → AI Router within a few moments.

Updating applications on your VPS

Applications deployed through the Hostinger Docker Catalog, store the API key as an environment variable.

  1. Open your VPS in Hostinger dashboard and go to Docker Manager
  2. Click Manage on the application you want to update
  3. Open the Environment tab
  4. Update the API key variable with your new sk-hstgr- key
  5. Update the base URL variable to https://router.hostinger.com/v1
  6. Click Deploy to re-deploy the container

Once the container restarts, the application is connected to Hostinger AI Router and all usage is billed against your credit balance.

New application installations already point to Hostinger AI Router, so only containers deployed before the migration need this change.

If you only use Hostinger managed applications

If your AI usage happens entirely inside Hostinger managed applications such as OpenClaw or Hermes Agent, you do not need to do anything. These applications are updated for you and will continue working without interruption.

Troubleshooting

My requests stopped working after the migration.
Your previous API key is no longer valid. Copy the new key from Hostinger dashboard → AI Router and make sure you have also changed the base URL to https://router.hostinger.com/v1. Updating only the key will not restore access.

I updated the key but requests still fail.
Check that the base URL has been changed as well, and that there is no trailing path left over from the previous configuration. The correct value ends in /v1.

My balance looks different.
Your balance is displayed in the new unit, where 1 previous credit equals 100 credits. The value is unchanged. If the converted figure does not match what you expect, contact our Customer Success team.

My balance is too low to run a request.
Your balance is checked before every request, so your credits can never go below zero. If your balance is too low to cover a request, the request is declined rather than charged. Top up at AI Router in Hostinger dashboard to resume.

What you get after migrating

Hostinger AI Router adds capabilities that were not available before:

  • One API key for leading models from every major provider, switched with a single parameter
  • Automatic fallback to another model if a provider becomes unavailable
  • Multiple API keys, each with its own daily and monthly spending limit and its own allowed models
  • Per-key usage in Hostinger dashboard, broken down by day and by model
  • One balance shared across Hostinger AI products, so a single top-up covers everything

Your existing code continues to work throughout, because Hostinger AI Router is compatible with the OpenAI and Anthropic APIs.