GPT-Image 2.6 Flare & Sunburst are liveImages from $0.025 each

API key setup

Claude API Key: Get, Configure & Test

To configure a Claude API key, first choose who issues it. Match the key to the API URL and model ID. The steps below set up access through OmniaKey.

Official provider key

For a key issued and billed directly by Anthropic, follow the provider’s own account and API key instructions.

Open official key instructions

OmniaKey API key

Use one OmniaKey balance and key for the models available to your account. The key works with the OmniaKey endpoint.

Get an API key

01Create an OmniaKey API key

Sign in, open API Keys and create a key for your application. Review its quota, expiry and model restrictions. Add balance before running generation requests.

Get an API key

02Set the key and API URL

Run the commands in your own terminal and replace the placeholder with your key. Keep the key on your server or in a secret manager. Never put it in browser code or a public repository.

bash / zsh
export OMNIAKEY_API_KEY="YOUR_OMNIAKEY_API_KEY"
export OMNIAKEY_BASE_URL="https://api.omniakey.com/v1"

03Check authentication

Request the model list without starting a generation job. A successful response is JSON with a data array. This checks key access; it does not prove every model is enabled for your account.

GET /v1/models
curl --fail-with-body "$OMNIAKEY_BASE_URL/models" \
  -H "Authorization: Bearer $OMNIAKEY_API_KEY"

04Use the model’s request format

Select a model from the family page, copy its API ID and follow the matching API documentation. Authentication alone does not check your generation parameters.

Your client must support the protocol used by the selected model. Check the model documentation before switching between Chat Completions, Responses or a provider-native endpoint.

Example generation request (billed)

This request uses your account balance. Check the selected model’s price first. The example follows the documented request format; your account still needs access to the model.

POST /v1/messages
curl --fail-with-body 'https://api.omniakey.com/v1/messages' \
  -H "Authorization: Bearer $OMNIAKEY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "anthropic-version: 2023-06-01" \
  -d '{
  "model": "claude-sonnet-5-5",
  "max_tokens": 256,
  "messages": [
    {
      "role": "user",
      "content": "Explain what an API key does in one sentence."
    }
  ]
}'
Read the API documentation

If the connection fails

  • 401: check that the key is complete, active and issued for the API URL you are calling.
  • 403: check the key’s model restrictions and the permissions available to your account.
  • 404 or HTML instead of JSON: check the API host and version prefix. Use api.omniakey.com, not the website address.
  • 429: reduce concurrency and follow the response’s retry guidance. Do not keep resubmitting generation jobs with new idempotency keys.