Search docs...

Start typing to search documentation

Platform Guide

Routers and agents

The three things that most often break a connection test.

Enter the base URL exactly as shown in Quickstart. Do not append /v1/messages or /v1/chat/completions, because the router adds the endpoint path itself.

bash
# Salah - base URL ikut memuat path endpoint
base_url = "https://oao.ai.id/v1/messages"   # router akan kirim ke /v1/messages/v1/messages

# Benar
base_url = "https://oao.ai.id"

A base URL that already ends in /v1/messages makes the router post to a path that does not exist, and you get a 404 or a vague error.

Routers probe the connection with a tiny request using the provider's default model. That model has to exist in your pack, otherwise the test fails even though the key is perfectly fine.

Set the default model to a name that matches your pack's model list exactly, character for character.

The models your pack can use are shown on the All Models page and, filtered to your pack, in your dashboard. Models, VIP and packs

This is the single most common support ticket. Check the model name before assuming the key is broken.

The message Invalid API key or base URL is your router's catch-all for every 401 and 403 rejection from OAO. It does not necessarily mean the key is wrong.

  • The base URL was entered down to /v1/messages. The base URL alone is enough.
  • The router's default model is not in your pack's list.
  • The key was used from too many IP locations within 24 hours, or it was revoked.

The full list of status codes and what each one means: Errors and rate limits

A router running on a VPS plus a VPN or WARP plus your laptop at the same time can easily exceed the location limit. That is not a bug, it is the limit doing its job.

Run the router from one fixed location without WARP, and the limit will not bother you.