{"id":19150,"date":"2026-09-30T10:02:11","date_gmt":"2026-09-30T10:02:11","guid":{"rendered":"https:\/\/www.hostinger.com\/support\/?p=19150"},"modified":"2026-10-08T04:39:32","modified_gmt":"2026-10-08T04:39:32","slug":"migrating-your-credits-from-nexos-ai-to-hostinger-ai-router-credits","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/migrating-your-credits-from-nexos-ai-to-hostinger-ai-router-credits\/","title":{"rendered":"Migrating your credits from nexos.ai to Hostinger AI Router credits"},"content":{"rendered":"

Hostinger AI Router<\/a> 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.<\/span><\/p>

All existing AI credits are moving to Hostinger AI Router<\/a>. 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.<\/span><\/p>

What changes<\/h2>

Three things change when your account moves to Hostinger AI Router<\/a><\/span>.<\/p>\n\n\n\n\n\n\n\n
What<\/th>\nBefore<\/th>\nAfter<\/th>\n<\/tr>\n<\/thead>\n
Base URL<\/td>\nhttps:\/\/api.nexos.ai\/v1<\/code><\/td>\nhttps:\/\/router.hostinger.com\/v1<\/code><\/td>\n<\/tr>\n
API key<\/td>\nYour previous key<\/td>\nA new Hostinger key starting with sk-hstgr-<\/code><\/td>\n<\/tr>\n
Model names<\/td>\nYour previous model IDs<\/td>\nShorter, simpler model names<\/td>\n<\/tr>\n
Credit balance<\/td>\nYour current balance<\/td>\nThe same value, converted at 1 credit to 100 credits<\/td>\n<\/tr>\n<\/tbody>\n<\/table>

What happens to your credit balance<\/h2>

Your balance is converted at a rate of 1 credit to 100 credits<\/strong>. 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.<\/p>

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.<\/p>

Your converted balance is always visible in Hostinger dashboard<\/strong> → AI Router<\/strong>, together with your usage for the current period.<\/div>

When the migration happens for you<\/h2>

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

If you still have credits and use them regularly<\/h3>

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

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.<\/p>

If you have credits but rarely use them<\/h3>

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.<\/p>

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.<\/p>

If you are a new customer<\/h3>

You already have Hostinger credits and a Hostinger API key. There is nothing to migrate.<\/p>

Switching before you are migrated<\/h2>

You do not have to wait. Once you have spent your existing nexos.ai credits<\/a> balance, you can buy Hostinger credits straight away at AI Router<\/a> 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.<\/p>

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

How to update your setup<\/h2>

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

Step 1 – Copy your new details<\/h3>
    \n
  1. Log in to Hostinger dashboard<\/a><\/li>\n
  2. Open AI Router<\/strong><\/li>\n
  3. Copy your API key from the API key<\/strong> section.<\/li>\n
  4. Note the base URL: https:\/\/router.hostinger.com\/v1<\/code><\/li>\n
  5. <\/code>Find a new model slug (you can find it on the Models<\/strong> page).<\/li>\n<\/ol>

    Step 2 – Replace them in your code<\/h3>

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

    from openai import OpenAI\r\n\r\nclient = OpenAI(\r\n    api_key=\"YOUR_KEY_HERE\",\r\n    base_url=\"https:\/\/router.hostinger.com\/v1\"\r\n)<\/code><\/pre>
    Step 3 – Replace them in your applications<\/h3>
    Update the same two values in every place you use AI, including automation workflows, coding tools, and any application running on your VPS.<\/p>
    Step 4 – Test a request<\/h3>
    Run a single request to confirm the connection works. Your usage appears in Hostinger dashboard → AI Router<\/strong> within a few moments.<\/p>
    Updating applications on your VPS<\/h2>
    Applications deployed through the Hostinger Docker Catalog, store the API key as an environment variable.<\/p>
      \n
    1. Open your VPS in Hostinger dashboard and go to Docker Manager<\/strong><\/li>\n
    2. Click Manage<\/strong> on the application you want to update<\/li>\n
    3. Open the Environment<\/strong> tab<\/li>\n
    4. Update the API key variable with your new sk-hstgr-<\/code> key<\/li>\n
    5. Update the base URL variable to https:\/\/router.hostinger.com\/v1<\/code><\/li>\n
    6. <\/code>Click Deploy<\/strong> to re-deploy the container<\/li>\n<\/ol>
      Once the container restarts, the application is connected to Hostinger AI Router and all usage is billed against your credit balance.<\/p>
      New application installations already point to Hostinger AI Router, so only containers deployed before the migration need this change.<\/div>
      If you only use Hostinger managed applications<\/h2>
      If your AI usage happens entirely inside Hostinger managed applications such as OpenClaw<\/a> or Hermes Agent, you do not need to do anything. These applications are updated for you and will continue working without interruption.<\/p>
      Troubleshooting<\/h2>
      My requests stopped working after the migration.<\/strong>
      \nYour previous API key is no longer valid. Copy the new key from Hostinger dashboard<\/strong> → AI Router<\/strong> and make sure you have also changed the base URL to https:\/\/router.hostinger.com\/v1<\/code>. Updating only the key will not restore access.<\/p>
      I updated the key but requests still fail.<\/strong>
      \nCheck 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<\/code>.<\/p>
      My balance looks different.<\/strong>
      \nYour 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.<\/p>
      My balance is too low to run a request.<\/strong>
      \nYour 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<\/a> in Hostinger dashboard to resume.<\/p>
      What you get after migrating<\/h2>
      Hostinger AI Router adds capabilities that were not available before:<\/p>
        \n
      • One API key for leading models from every major provider, switched with a single parameter<\/li>\n
      • Automatic fallback to another model if a provider becomes unavailable<\/li>\n
      • Multiple API keys, each with its own daily and monthly spending limit and its own allowed models<\/li>\n
      • Per-key usage in Hostinger dashboard, broken down by day and by model<\/li>\n
      • One balance shared across Hostinger AI products, so a single top-up covers everything<\/li>\n<\/ul>
        Your existing code continues to work throughout, because Hostinger AI Router is compatible with the OpenAI and Anthropic APIs.<\/p>\n","protected":false},"excerpt":{"rendered":"
        See when your nexos.ai credits migrate and how to update your API setup.<\/p>\n","protected":false},"author":568,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"include_on_kodee":true,"footnotes":""},"categories":[321],"tags":[],"class_list":["post-19150","post","type-post","status-publish","format-standard","hentry","category-hostinger-ai-router"],"hreflangs":[],"include_on_kodee":true,"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/19150","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/users\/568"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/comments?post=19150"}],"version-history":[{"count":9,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/19150\/revisions"}],"predecessor-version":[{"id":19878,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/19150\/revisions\/19878"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/media?parent=19150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/categories?post=19150"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/tags?post=19150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}