API returns "Internal server error" with "Authenticate" even with valid API key – Service appears to be down

[joaobrunon]

Markdown### Description

The API is returning an authentication/internal server error even when using a freshly generated valid API key from the dashboard.

Exact error returned:

{
  "message": "Internal server error",
  "error": "Authenticate"
}
Steps to Reproduce

Created a new account at https://www.omkar.cloud/
Generated a new valid API key (starts with ok_)
Used the official command from the README:

Bashcurl -s -G "https://carrier-lookup-api.omkar.cloud/lookup" \
  -H "API-Key: ok_YOUR_KEY_HERE" \
  --data-urlencode "phone=+5511998765432" | jq

Also tested the query-string version:

Bashcurl -s "https://carrier-lookup-api.omkar.cloud/lookup?phone=%2B5511998765432" \
  -H "API-Key: ok_YOUR_KEY_HERE"
Expected Behavior
Should return a JSON response with:

is_valid_number
line_type (mobile/landline/voip)
carrier (Vivo, Claro, TIM, etc.)
national_format, country_code, etc.

Actual Behavior
Always returns:
JSON{
  "message": "Internal server error",
  "error": "Authenticate"
}
Additional Information

Tested with multiple Brazilian numbers (+55)
Tested with keys created at different times
Tested on different machines (Linux WSL2)
The endpoint carrier-lookup-api.omkar.cloud appears to be offline (connection refused in some tests)
Repository has no updates since 2024
Dashboard still allows creating keys, but the backend API does not respond

Environment

OS: Linux (WSL2 - Ubuntu)
Tool: curl + jq
Date: March 22, 2026