API overview

MyIP OpenRouter's /api/v1 uses the same request and response shapes as the OpenAI Chat Completions API. If you already have code written against the OpenAI SDK — or against openrouter — changing the base URL and the API key is enough.

Exactly one thing differs: amounts are in KRW. Field names, nesting, and the convention of encoding decimals as strings are all identical to openrouter. The fact that a number is won (₩) rather than dollars is pinned down by the X-MyIP-Currency: KRW header on every response and by the pricing.currency field.

Base URL

https://openrouter.myip.co.kr/api/v1

Endpoints

Any /api/v1 path not in this table returns 404 not_supported. It is not a silent 404 — the body names the path that does not exist. See Unsupported endpoints for the full list.

Two kinds of key

Using one where the other is expected returns 401 invalid_api_key. /api/v1 is an SDK surface, so it never accepts cookies — the dashboard screens that manage keys use their own session-authenticated API. Authentication has the details.

Your first request

curl https://openrouter.myip.co.kr/api/v1/chat/completions \
  -H "Authorization: Bearer $MYIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "google/gemma-4-26b-a4b",
    "messages": [{"role": "user", "content": "Introduce yourself in one sentence."}]
  }'

Response headers

Request headers

HTTP-Referer and X-Title deliberately keep their openrouter names so that existing code does not have to rename headers. See App attribution.

Errors

The error body has the same shape on every path. The HTTP status code and error.code are always equal.

{
  "error": {
    "code": 402,
    "message": "크레딧이 부족합니다.",
    "metadata": { "error_type": "insufficient_credits", "balance_krw": "-5200.000000" }
  }
}

The complete status / error_type pairing lives in Errors and debugging.

How far compatibility goes

• Supported: text chat, streaming, tool calling, structured outputs, model fallbacks (models[]), provider routing (provider{}), usage and cost lookups.
• Not supported: embeddings, image/video/audio, the Responses API, Batch, Presets, Workspaces, Guardrails, BYOK, OAuth, SCIM, Auto Router, and model variants such as :free or :nitro. All of them return 404 not_supported.

There is one thing we have that openrouter does not: when a model is loaded on our own GPU farm, it is tried before any external provider (Local-first routing).