Quickstart

Point base_url at ApiGo, keep your OpenAI-compatible SDK, and finish in a few minutes.

1. Create an API key

Open Workspace (sign in if needed).
Go to API Keys.
Create a key. Store it as an environment variable — never embed it in frontend code.

export APIGO_API_KEY=sk-apigo-...

2. Set the base URL

https://api.apigo.ai/v1

List available models with:

curl https://api.apigo.ai/v1/models \
  -H "Authorization: Bearer $APIGO_API_KEY"

3. Choose a model ID

Open Models and copy the exact slug shown there. For this OpenAI-compatible quickstart, use a model that supports Chat Completions, for example:

gpt-5.6-sol
qwen3.8-max
deepseek-v4-flash

4. Send a request

cURL

curl https://api.apigo.ai/v1/chat/completions \
  -H "Authorization: Bearer $APIGO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.6-sol",
    "messages": [
      {"role": "user", "content": "Explain ApiGo in one sentence."}
    ]
  }'

Python

from openai import OpenAI

client = OpenAI(
    base_url="https://api.apigo.ai/v1",
    api_key="$APIGO_API_KEY",
)

response = client.chat.completions.create(
    model="gpt-5.6-sol",
    messages=[
        {"role": "user", "content": "Explain ApiGo in one sentence."},
    ],
)

print(response.choices[0].message.content)

JavaScript

import OpenAI from "openai"

const client = new OpenAI({
  baseURL: "https://api.apigo.ai/v1",
  apiKey: process.env.APIGO_API_KEY,
})

const response = await client.chat.completions.create({
  model: "gpt-5.6-sol",
  messages: [
    { role: "user", content: "Explain ApiGo in one sentence." },
  ],
})

console.log(response.choices[0].message.content)

5. Verify in the workspace

After the first call:

Open Workspace → Call Logs to inspect status, latency, and the model that answered.
Open Workspace → Usage for spend and request trends.
Open Workspace → Billing if you need to top up (USD via Stripe).

Common errors

Code	Meaning	What to do
`401 invalid_api_key`	Key missing, wrong, or revoked	Check Bearer header; confirm the key is enabled under Workspace → API Keys
`402 insufficient_balance`	Workspace balance is empty	Top up under Workspace → Billing
`429 rate_limited`	Provider or account rate limit	Retry later, or add a fallback chain under Workspace → Routing
`503 upstream_unavailable`	Upstream model temporarily down	ApiGo follows your routing policy; inspect Call Logs for the attempted providers

Next steps

Platform overview — how Workspace modules fit together
Models catalog — filters, pricing, and IDs
API Reference — full request/response schemas

Introduction

Overview