Skip to content

Antigravity

Antigravity dedicated paths force requests to use only the Antigravity account pool instead of normal mixed scheduling.

Model Lists

MethodPathNotes
GET/antigravity/modelsAntigravity model list.
GET/antigravity/v1/modelsAntigravity v1 model list.

Request example:

bash
curl https://llmapi.site/antigravity/models \
  -H 'Authorization: Bearer YOUR_API_KEY'

Messages

ItemValue
MethodPOST
Path/antigravity/v1/messages
Content-Typeapplication/json
bash
curl https://llmapi.site/antigravity/v1/messages \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "model": "claude-sonnet-4-5",
    "max_tokens": 512,
    "messages": [
      { "role": "user", "content": "Hello" }
    ]
  }'

Token Count and Usage

MethodPathNotes
POST/antigravity/v1/messages/count_tokensToken count compatible entry.
GET/antigravity/v1/usageUsage and quota information for the current key.

Gemini Native Compatibility

MethodPathNotes
GET/antigravity/v1beta/modelsModel list.
GET/antigravity/v1beta/models/{model}Model details.
POST/antigravity/v1beta/models/{model}:generateContentGemini native compatible generation.
POST/antigravity/v1beta/models/{model}:streamGenerateContent?alt=sseGemini native compatible streaming.

For regular integrations, prefer the standard /v1 and /v1beta paths. Use /antigravity only when dedicated Antigravity routing is required.