Authentication

Every request to Helmcode is authenticated with a Bearer API key sent against the base URL. The API is OpenAI-compatible — any OpenAI SDK handles this for you.

Base URL

https://api.helmcode.com/v1

API keys

API keys are issued per workspace from the Dashboard → API Keys. They belong to your organization — not to you personally — and can be created or revoked at any time. The number of keys available depends on your plan — 5 on Starter, 15 on Growth, 40 on Scale.

Treat keys like passwords: store them server-side as environment variables, never commit them to source control, never ship them in client-side code.

Authorization header

Send your key in the Authorization header on every request:

Authorization: Bearer sk-your-key-here

Examples

cURL

curl https://api.helmcode.com/v1/models \
  -H "Authorization: Bearer $HELMCODE_API_KEY"

Python

import os
from openai import OpenAI

client = OpenAI(
    base_url="https://api.helmcode.com/v1",
    api_key=os.environ["HELMCODE_API_KEY"],
)

Errors

A missing or invalid key returns 401 Unauthorized. For 429 Too Many Requests, see Rate limits.

Warning: a model id your key cannot reach returns the same 401, with the message This API key does not have access to the requested model. A typo is indistinguishable from a permissions problem: glm-5.3 and glm5.3 fail and succeed respectively, and the error for the first one reads like your plan is missing something. Before assuming it is access, check the id against Models character by character.