Quick start

Verify email → create an API key → choose a text model → run cURL.

Open Quick start in your account. It shows account readiness and inserts the selected accessible API key and model ID into the command. Copying does not send a request.

In your account, choose the terminal tab: Linux / macOS · Bash, Windows · PowerShell or Windows · CMD. A model change updates every command; selecting or copying a tab sends no request. Windows · CMD opens by default, with only one terminal pane visible. Without JavaScript, a CMD template remains; automatic key insertion and media recipes require JavaScript.

When your company requires 2FA, Quick start is readable before enrollment, including from the notice in Profile. Keys, the available-model list and company resources remain locked. A command containing MODEL_ID is only a template. Complete Profile → Authenticator app (TOTP) and then return to the guide. An existing temporary-password change requirement still takes precedence.

1. Verify your email

Open the link in the verification email. Resend it from your account if needed. Company review and activation after agreement on terms are separate from email verification. If another verified sign-in method already permits API access, follow the account’s displayed access state.

2. Create or select a key

Open API Keys, create “First request” and store the full value securely. An existing accessible active key can also be used. Ask your company or project administrator if your role cannot create keys.

Keep the key locally in an environment variable or secret manager. Never send it to support or publish it in browser code or a public repository. In the account guide the first available revealable key is selected automatically. Its full value is loaded using the existing protected key access check; complete recent 2FA and reload when requested. If none exists, create a key. Commands and copies contain your secret: do not share them. This public guide below contains YOUR_API_KEY only.

3. Choose a model

Choose an available text model supporting Chat Completions and check applicable prices. Replace MODEL_ID below with its exact ID. The account’s Quick start inserts the model ID automatically.

4. Send the request

This command is for Bash and cURL. Replace YOUR_API_KEY locally with your key.

export MODEL_API_KEY='YOUR_API_KEY'

curl 'https://api.b2b-llm.com/v1/chat/completions' \
  -H "Authorization: Bearer $MODEL_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{"model":"MODEL_ID","messages":[{"role":"user","content":"Reply with one short greeting."}],"stream":false}'

On success, expect HTTP 200 and JSON. The answer is in choices[0].message.content; wording can differ. The request is charged at the applicable tariff. Review status and cost in Usage.

PowerShell command

For Windows PowerShell 5.1 or PowerShell 7, use the native Invoke-RestMethod, not a curl alias. The body is encoded explicitly as UTF-8. Replace the key locally only.

$env:MODEL_API_KEY = 'YOUR_API_KEY'

$body = @'
{
    "model": "MODEL_ID",
    "messages": [
        {
            "role": "user",
            "content": "Reply with one short greeting."
        }
    ],
    "stream": false
}
'@

Invoke-RestMethod -Uri 'https://api.b2b-llm.com/v1/chat/completions' `
  -Method Post -UseBasicParsing -MaximumRedirection 0 `
  -Headers @{ Authorization = "Bearer $env:MODEL_API_KEY" } `
  -ContentType 'application/json; charset=utf-8' `
  -Body ([System.Text.Encoding]::UTF8.GetBytes($body)) | ConvertTo-Json -Depth 50

CMD command

Use Windows Command Prompt (cmd.exe) with curl.exe installed. This syntax is not for PowerShell.

set "MODEL_API_KEY=YOUR_API_KEY"

curl.exe "https://api.b2b-llm.com/v1/chat/completions" ^
  -H "Authorization: Bearer %MODEL_API_KEY%" ^
  -H "Content-Type: application/json" ^
  --data-raw "{\"model\":\"MODEL_ID\",\"messages\":[{\"role\":\"user\",\"content\":\"Reply with one short greeting.\"}],\"stream\":false}"

If the request fails

Check the API address, key, model ID, activation and limits. Read the error body. After a timeout, check history first: work may already have completed. Do not use automatic paid retries to inspect status. Give support the request ID and error code, not your secret key.

Next steps

Use the API reference for parameters, formats and limits. Model features differ; images, transcription and video have their own Playground and API workflows.

Direct provider access

This example is for the B2B LLM gateway. For direct access, use the address, keys, models and terms from your company’s offer. Do not send a gateway key to a provider endpoint.

Simple media commands

Below the account guide's text example, choose Images, Audio or Video and an available model/route. Recipes come only from active reviewed contracts and include your selected key. Audio means file transcription, not speech synthesis.

Run Create once, copy the accepted operation's id into Operation ID, then run Status and, after completion, Result. For Video, Download MP4 retrieves the file; Result returns JSON. For Audio, provide your own file with the suggested extension. PowerShell's multipart Audio recipe requires PowerShell7+; Windows CMD/curl.exe is an alternative.

Windows · CMD is the default tab. Tabs, operation ID editing and Copy do not submit requests. GET does not start a new generation. Use New request ID (no send) for separate new work, not for retrying an uncertain paid submission: check its saved status first. Missing reviewed routes produce an unavailable explanation, not an invented model.