JamesZhaoY / logicc2api

# logicc2api
**English** · 简体中文
This button creates a new Git repository. If you already have this project in your Git account, use Deploy from an existing repository.
> **Disclaimer:** Please read the disclaimer and usage responsibilities (Simplified Chinese) before use. It covers account authorization, third-party service risks, data handling, and limitations of liability. The MIT License continues to govern the software license.
An OpenAI-compatible adapter for Logicc, with account pool management and a web console. Run it with Node.js, Docker, or Cloudflare Workers. It converts Logicc's AI SDK v6 event stream into OpenAI Chat Completions / Responses and Anthropic Messages responses and shows account health, traffic, latency, and request history in one place.
Built with Node.js and plain HTML/CSS/JavaScript. **No runtime dependencies, database setup, or frontend build step.** The web interface is currently in Simplified Chinese; documentation is available in English and Chinese.
## Features
| Area | What it provides |
| --- | --- |
| Protocol compatibility | Model listing; JSON and SSE for Chat Completions, Responses, and Messages |
| Client tool calls | Standard tool_calls / function_call / tool_use and matching tool-result round trips |
| Account pool | Add, edit, remove, enable/disable, search, and bulk-import accounts |
| Upstream assistant prompts | Read, back up, edit, and publish assistant systemPrompt; select a default assistant per account |
| Credential refresh | On-demand Clerk JWT refresh, shared concurrent refreshes, and persistence of rotated client cookies |
| Scheduling | Prefer the least-busy accounts, round-robin between ties, and cool down failing accounts |
| Dashboard | Request trends, success rate, time to first text, and account availability |
| Models and logs | Live model discovery, observed model latency, request details, filters, and CSV export |
| Playground | Send a real streaming request, choose an upstream tool, and stop the local request |
| Persistent storage | Local files for Node/Docker; SQLite-backed Durable Object for Workers; raw cookies and JWTs are omitted from management responses |
| Cloudflare deployment | Deploy button, automatic resource setup, password-protected console, and a separate API key |
The console polls the adapter every five seconds. Account checks and model synchronization fetch the upstream model list; the playground sends real generation requests and uses your upstream quota.
## Quick start
Requires **Node.js 22 or newer** and a Logicc account/session you can use. For a container-based setup without installing Node.js on the host, see Docker deployment.
 [code] 
There is no dependency installation step. You can also run `node server.mjs` directly.
1. Open ** **.
2. Go to **号池管理 → 添加账户** (Account pool → Add account), enter your credentials, and click **检测** (Check).
3. Point your client at **`http://127.0.0.1:18789/v1`**. Unless you configure `LOGICC_API_KEY`, use any non-empty API key