How qqlishili/zcode2api works
zcode2api is a self-hosted account-management console and dual-protocol AI gateway. Client requests enter the gateway, are authenticated and translated as needed, then routed through the account pool to an upstream provider; responses and request activity return through that gateway. Separate operational workflows cover account onboarding, OAuth, device/install identity, quota monitoring, and time-limited plan claims. The graph follows README capabilities and sampled routes/lifecycle wiring; several unsampled subsystems use their documented paths, with uncertain internal call links omitted.
Main entry points: gateway.py Gateway routes · admin_api.py Admin API · main.py Application lifecycle · store.py Account store
Components 24
API gateway
- Gateway routes
app/routes/gateway.py - Gateway auth
app/auth_admin.py - OpenAI translation
app/openai_compat.py - Header cleaning
app/body_transform.py - Upstream client
app/agent.py
Account operations
- Account store
app/store.py - Account state
app/models.py - Device fingerprints
app/fingerprint.py - Install sequence
app/install.py - OAuth login
app/oauth.py - Plan claims
app/claim.py - Quota monitor
app/quota.py
Admin console
- Admin API
app/routes/admin_api.py - Admin pages
app/routes/pages.py - Admin interface
frontend/admin/accounts.html - CLI
cli.py
Runtime services
- Captcha manager
app/captcha.py - Captcha solver
captcha_node/solver.js - Activity sentinel
app/sentinel.py - Request monitoring
app/reqlog.py - Application lifecycle
app/main.py
Other components
- API clients
- AI providers
- Aliyun captcha
Connections 30
- API clients → Gateway routes: submit requests
- Gateway routes → Gateway auth: checks access
- Gateway routes → OpenAI translation: translates OpenAI
- Gateway routes → Header cleaning: cleans headers
- Gateway routes → Account store: selects accounts
- Gateway routes → Upstream client: forwards requests
- Upstream client → AI providers: calls upstream
- Gateway routes → Captcha manager: gets verification
- Gateway routes → Request monitoring: records activity
- Account store → Account state: loads state
- CLI → OAuth login: starts login
- OAuth login → AI providers: authorizes
- CLI → Account store: adds accounts
- Admin interface → Admin pages: loads pages
- Admin interface → Admin API: calls admin APIs
- Admin API → Gateway auth: requires credentials
- Admin API → Account store: manages accounts
- Admin API → Quota monitor: refreshes quotas
- Admin API → Plan claims: requests claims
- Plan claims → AI providers: claims plans
- Quota monitor → AI providers: fetches quotas
- Captcha manager → Captcha solver: invokes process
- Captcha solver → Aliyun captcha: solves challenge
- Application lifecycle → Quota monitor: starts monitor
- Application lifecycle → Captcha manager: starts manager
- Application lifecycle → Activity sentinel: starts sentinel
- Application lifecycle → Install sequence: runs startup sequence
- Application lifecycle → Account store: backfills account data
- Admin API → Device fingerprints: rotates profiles
- Install sequence → AI providers: reports activation