Clients/WorkBuddy

Use the Wokey API with WorkBuddy

Get a Wokey API key, point WorkBuddy at the Wokey base URL, then confirm the connection with one curl request.

Updated

On this pageexpand_more

Get an API key and the base URLlink

Every client uses the same Wokey API key and the same base URL.

Create an API key

Sign in and create a platform key on the API page. Keys in one account share its balance.

Create an API keykey

Use the Wokey base URL

Set the client base URL to the gateway domain; the configuration below shows whether to append /v1.

Configure the clientlink

WorkBuddy uses OpenAI Chat Completions for custom models. In WorkBuddy, open Settings → Model → Custom models and enter Wokey’s endpoint, API key, and deepseek-flash; tool calls and image input can then be used by WorkBuddy tasks and agent workflows.

  1. 1

    Open model settings

    Click the account button in the lower-left corner of WorkBuddy → Settings → Model. You can also open the model selector and choose Configure custom model.

  2. 2

    Add a custom model

    Choose Custom. Set the endpoint to https://api.wokey.ai, paste your Wokey API key, and enter the exact model ID deepseek-flash. Do not use the display name DeepSeek-V4.1-Flash as the model ID.

  3. 3

    Set capabilities

    Enable tool calling and image input. Leave reasoning mode and custom protocol off. deepseek-flash accepts text, images, and tools; if you use deepseek-v4-flash instead, turn image input off because that model is text-only.

  4. 4

    Save and switch models

    Run Test connection, save the model, then select it from the conversation model picker. Start with a short text prompt before testing tools or images.

WorkBuddy
Provider: Custom
Endpoint: https://api.wokey.ai
API key: YOUR_API_KEY
Model: deepseek-flash
Tool calling: On
Image input: On
Reasoning mode: Off
Custom protocol: Off

Common troubleshootinglink

  • 404: keep the endpoint at https://api.wokey.ai and leave custom protocol off. Only when custom protocol is on should you enter the full https://api.wokey.ai/v1/chat/completions path.
  • 401: paste the key itself into the API key field; do not add the Bearer prefix. Confirm the key is active and the account has balance.
  • model_not_found: the model ID must be deepseek-flash. DeepSeek-V4.1-Flash is the display name, not the Wokey model ID.
  • Image requests fail: select deepseek-flash and enable image input. deepseek-v4-flash accepts text only.
  • 429, 502, 504, or 529: reduce concurrency, shorten the context, or retry later; you can also switch to another available model.

Verify with curllink

If the client reports an error, rule out the key and base URL with curl first.

WorkBuddy uses the OpenAI Chat Completions format by default. A 200 from this request means the key and base URL are right. Replace YOUR_API_KEY with your key before sending it.

cURL
curl https://api.wokey.ai/v1/chat/completions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "deepseek-flash",
    "messages": [
      { "role": "user", "content": "Hello" }
    ]
  }'

Errors & Troubleshootinglink

Separate auth, balance, rate limit, model availability, and upstream timeout cases first.

401

invalid api key

The key is missing, mistyped, deleted, or Authorization / x-api-key headers conflict.

402

insufficient balance

The account balance is too low. Top up before sending more requests.

403

model_denylisted / account_restricted

Calls to the model, or to every model on the account, are paused after repeated violations. See Violation Handling Fees & Restrictions.

403

request_blocked

This request was blocked before reaching the upstream and is not charged, for example an unchanged resend of a request the model just refused, or a paused end user (X-End-User-Id). The error message says what is blocked; change the request as it says or retry later. Other requests are not affected.

429

rate limited

Traffic is too frequent. Retry later or reduce concurrency. If only one model, or one end user (X-End-User-Id), keeps returning 429, it may be a temporary limit after violations.

502

upstream unavailable

The upstream model service is temporarily unavailable. Switch models or retry later.

504

upstream timeout

The upstream response timed out. Shorten context, reduce max_tokens, or retry.

529

upstream overloaded

The upstream model is temporarily overloaded and Wokey already retried on other routes (code upstream_overloaded). It is unrelated to your balance. Retry shortly or switch models.