tonhowtf/omniget · error

xAI HTTP {}: {}

Error message

xAI HTTP {}: {}

What it means

ask_xai calls the official xAI API (POST https://api.x.ai/v1/responses) and, when the HTTP status is not a success (2xx), it extracts the error message from the JSON body (error.message or error) and returns `xAI HTTP <status>: <message>`. This is the library's generic wrapper for any non-2xx response from the xAI API — auth failures, bad model names, rate limits, invalid parameters all surface through it.

Solutions

1. Check the status code and message in the error text: 401/403 means fix the xai_key (re-run grok set with a fresh key from console.x.ai).
2. If 400/404 mentions the model, set a valid xai_model (e.g. grok-4.6) in grok.json or pass req.model.
3. If 429, wait and retry with backoff or reduce request frequency.
4. If 5xx, retry later; it is a server-side xAI outage.
5. Verify network/proxy settings if the status indicates connectivity errors.

Example fix

// before
body = json!({ "model": "grok-2-121345", ... })  // retired model -> xAI HTTP 400
// after
body = json!({ "model": "grok-4.6", ... })  // valid current model

let cfg = grok_config();
if cfg.xai_key.trim().is_empty() { return Err("configure xai_key first"); }
if !cfg.xai_model.starts_with("grok-") { return Err("xai_model looks invalid"); }

fn status_is_retryable(status: u16) -> bool { status == 429 || status >= 500 }

match grok::ask(req).await {
    Ok(a) => use_answer(a),
    Err(e) if e.to_string().contains("xAI HTTP 401") => reconfigure_key_and_retry(),
    Err(e) if e.to_string().contains("xAI HTTP 429") => sleep_backoff_and_retry(),
    Err(e) => log_error(e),
}

When it happens

Trigger: The /v1/responses call returns 401 (invalid/expired xai_key), 400 (unknown xai_model, malformed tools/instructions payload), 403, 429 (rate limit), or 5xx; any non-success status with a JSON body triggers this error.

Common situations: Stale or missing XAI API key after rotation; typo'd or retired model name in grok.json (xai_model); exceeding xAI quota/rate limits; passing search tools the account/plan does not allow.

Understand the failure class

Background: "API error: {status}" and "HTTP 401/403/404/429/5xx" errors: non-2xx HTTP responses explained — this error's family across 27 libraries.

Related errors

• HTTP {}
• {}
• LibreTranslate: HTTP {} {}
• VoiceStudio HTTP {}: {}
• criar perfil: {}

AI-assisted analysis of tonhowtf/omniget@8600b91f42 (2026-09-12). Data as JSON: /api/errors/3a2438b3cc78f5f6. Report an issue: GitHub.

Appendix: source

Thrown at src-tauri/omniget-core/src/core/tools/x/grok.rs:200

    let resp = client
        .post("https://api.x.ai/v1/responses")
        .bearer_auth(&cfg.xai_key)
        .json(&body)
        .send()
        .await?;
    let status = resp.status();
    let v: Value = resp
        .json()
        .await
        .map_err(|e| anyhow!("xAI: resposta invalida ({})", e))?;
    if !status.is_success() {
        let msg = v
            .pointer("/error/message")
            .or_else(|| v.get("error"))
            .and_then(|m| m.as_str())
            .unwrap_or("erro")
            .to_string();
        return Err(anyhow!("xAI HTTP {}: {}", status, msg));
    }
    let mut text = String::new();
    let mut citations: Vec<Citation> = Vec::new();
    for item in v
        .get("output")
        .and_then(|o| o.as_array())
        .into_iter()
        .flatten()
    {
        if item.get("type").and_then(|t| t.as_str()) != Some("message") {
            continue;
        }
        for c in item
            .get("content")
            .and_then(|c| c.as_array())
            .into_iter()
            .flatten()
        {

View on GitHub (pinned to 8600b91f42)