Cloud API Endpoint Status — 2026-07-05

Status: DOWN

All known LobeHub Cloud API endpoints return 404 or "DEPLOYMENT_NOT_FOUND":

https://api.lobehub.com/v1/chat/completions    → 404 "DEPLOYMENT_NOT_FOUND" (Vercel)
https://cloud.lobehub.com/v1/chat/completions  → 404 "DEPLOYMENT_NOT_FOUND" (Vercel)
https://app.lobehub.com/api/v1/chat/completions → 404 "404 Not Found"
https://app.lobehub.com/api/chat/completions   → 404 (Next.js error page)

What Works

Login: POST /api/auth/sign-in/email — 200 OK with session cookies
Signup: POST /api/auth/sign-up/email — 200 OK (creates account)
tRPC API key management: GET /trpc/lambda/apiKey.getApiKeys, POST /trpc/lambda/apiKey.createApiKey — 200 OK
Web app: app.lobehub.com loads fine, all pages work

Keys Created

Account: [REDACTED-EMAIL] (verified) 4 API keys created via tRPC, format hex:hex:hex (102 chars each). Keys are valid but unusable until the API gateway is redeployed.

Auth Format (untested — gateway is down)

The API key format is hex26:hex32:hex37. The auth header format is unknown:

Authorization: Bearer <key> — likely correct (OpenAI-compatible)
x-api-key: <key> — alternative
Custom header — unknown

Workaround

Use the LobeHub CLI (lh generate text) with session cookies instead of API keys. Or use the self-hosted proxy (:20140) which routes through the CLI.

1.4 KiB Raw Blame History