Why is my API Key invalid? - GravitexAI Documentation

Common Error

When you see an error like this:

{
  "error": {
    "message": "Incorrect API key provided: sk-QqHvK***...",
    "type": "invalid_request_error",
    "code": "invalid_api_key"
  }
}

This usually isn’t a problem with your API Key itself, but rather a Base URL misconfiguration.

Most common mistake: Using GravitexAI’s Key but the request URL still points to OpenAI’s https://api.openai.com

What is Base URL?

Base URL is the target server address for API requests. Different providers use different Base URLs.

Base URL and API Key Must Match

Provider	Base URL	API Key Format	Match?
GravitexAI	https://api.gravitex.ai	sk-xxxx…	✅ Correct
OpenAI Official	https://api.openai.com	sk-xxxx…	✅ Correct
❌ GravitexAI Key	https://api.openai.com	sk-xxxx…	❌ Wrong
❌ OpenAI Key	https://api.gravitex.ai	sk-xxxx…	❌ Wrong

Key principle: Use the provider’s Base URL that matches your API Key

Correct Configuration

Method 1: Modify Base URL (Recommended)

Python
Node.js
cURL

from openai import OpenAI

client = OpenAI(
    api_key="sk-your-gravitex-key",
    base_url="https://api.gravitex.ai/v1"
)

response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "Hello"}]
)

import OpenAI from 'openai';

const client = new OpenAI({
  apiKey: 'sk-your-gravitex-key',
  baseURL: 'https://api.gravitex.ai/v1'
});

const response = await client.chat.completions.create({
  model: 'gpt-4o',
  messages: [{ role: 'user', content: 'Hello' }]
});

curl https://api.gravitex.ai/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer sk-your-gravitex-key" \
  -d '{
    "model": "gpt-4o",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

Method 2: Environment Variables

Linux/macOS
Windows PowerShell
Windows CMD

export OPENAI_API_KEY="sk-your-gravitex-key"
export OPENAI_BASE_URL="https://api.gravitex.ai/v1"

$env:OPENAI_API_KEY="sk-your-gravitex-key"
$env:OPENAI_BASE_URL="https://api.gravitex.ai/v1"

set OPENAI_API_KEY=sk-your-gravitex-key
set OPENAI_BASE_URL=https://api.gravitex.ai/v1

Supported URL Formats

Format	URL	Use Case
With /v1 (recommended)	`https://api.gravitex.ai/v1`	Most libraries
With trailing slash	`https://api.gravitex.ai/v1/`	Some frameworks
Full path	`https://api.gravitex.ai/v1/chat/completions`	cURL requests

Troubleshooting

Changed Base URL but still getting errors

Possible causes:

Multiple configurations: Check config files, env vars, code initialization
Proxy or middleware: Some tools may redirect requests
Cache issues: Restart program or clear cache
Typos: Verify the URL spelling

How to verify Key is valid?

Check in GravitexAI console:

Login to GravitexAI
Go to “Tokens” page
Check if Key status is “Enabled”
Confirm account balance is sufficient

How to configure third-party tools?

Most tools have “Custom API” options:

API URL / Base URL: https://api.gravitex.ai/v1
API Key: Copy from GravitexAI console
Model name: Refer to model list

Wrong vs Correct Examples

❌ Wrong Configuration

client = OpenAI(
    api_key="sk-gravitex-key",
    base_url="https://api.openai.com/v1"
    # ❌ Using OpenAI's URL
)

Result: OpenAI server rejects GravitexAI’s Key

✅ Correct Configuration

client = OpenAI(
    api_key="sk-gravitex-key",
    base_url="https://api.gravitex.ai/v1"
    # ✅ Using GravitexAI URL
)

Result: Request successfully sent to GravitexAI

Quick Test

Verify configuration with cURL:

curl https://api.gravitex.ai/v1/models \
  -H "Authorization: Bearer sk-your-gravitex-key"

Expected result: Returns available models list

{
  "data": [
    {
      "id": "gpt-4o",
      "object": "model"
    }
  ]
}

If you get an error, check:

API Key copied correctly (no extra spaces)
Network connection is working
Account balance is sufficient

Remember: Match the Key to its URL. GravitexAI Key uses https://api.gravitex.ai/v1

​Common Error

​What is Base URL?

​Base URL and API Key Must Match

​Correct Configuration

​Method 1: Modify Base URL (Recommended)

​Method 2: Environment Variables

​Supported URL Formats

​Troubleshooting

​Wrong vs Correct Examples

​❌ Wrong Configuration

​✅ Correct Configuration

​Quick Test

Common Error

What is Base URL?

Base URL and API Key Must Match

Correct Configuration

Method 1: Modify Base URL (Recommended)

Method 2: Environment Variables

Supported URL Formats

Troubleshooting

Wrong vs Correct Examples

❌ Wrong Configuration

✅ Correct Configuration

Quick Test