Verified access
Approved organization email addresses use passwordless verification before an account or API key is issued.
About the service
A secure front door to shared models
Yihua API Console gives approved people one place to obtain API (Application Programming Interface) access, manage credentials, and understand usage without exposing the model infrastructure behind it.
Why it exists
Built for useful access with clear boundaries
The console turns a shared AI (Artificial Intelligence) service into a manageable workspace for both API users and operators.
Credential control
Users can separate keys by device or service, review their status, and revoke a credential immediately when needed.
Privacy-aware insights
Request, token, and model usage are available for review, while prompt and response content are not stored.
Design commitments
Security is part of the workflow
- 01
Complete API keys are revealed only once and are never stored by the portal.
- 02
Secure server-side sessions and CSRF (Cross-Site Request Forgery) protection guard account actions.
- 03
Administrative interventions require reasons and remain visible in an audit trail.
Change history
Major updates
Selected milestones from the service history, newest first.
Messaging integration and delivery reliability
Added a restricted QQ Bear administrator email relay and pooled SMTP (Simple Mail Transfer Protocol) delivery for more reliable verification messages.
Localization and model governance
Added English, Traditional Chinese, and Simplified Chinese experiences, plus centralized controls for public model availability.
Operational safeguards
Introduced service health monitoring, user and key controls, emergency pause and recovery, and administrator audit records.
Secure self-service workspace
Added verified email sign-in, protected sessions, API key lifecycle management, and detailed usage history.
Gateway and portal foundation
Launched the OpenAI-compatible gateway and the first verified-email API access portal.