Built-in Translation Layer (local dictionary + open-source engine)

Honesty note: all 21 integrations on this page are currently 【simulated】; the related features you see in the system run on demo data. Free & open-source first constitution: when results are equal, use free/open-source, local configuration, or self-built code; paid APIs are quality fallback only (default ~95% local/open-source + 5% paid fallback). To connect, you apply for an account & key on each official site; keys are NEVER entered into this system — configuration is done hands-on on your computer during a remote session. Customer-send / price-change / publish / production-DB actions always go through Human-Gate.

Built-in Translation Layer (local dictionary + open-source engine) P3

Infrastructure · Implementation route: Local Open-Source · Preferred · Current status: Key Ready

Purpose	Local dictionary + open-source translation engine (e.g. OPUS/M2M100, called via the /translate/ page) for Chinese/Indonesian/English
Unlocked after connecting	CS translation fully local and free; paid API only as fallback when quality falls short
Where to apply (official site)	本机内置 /translate/
Estimated cost	$0 (runs locally); paid fallback only when quality is insufficient
What you provide	No signup; reuse the built-in /translate/ translation layer
Connection priority	P3
Implementation route	Local Open-Source · Preferred
Current status	Key Ready

Simple Application Steps (5 steps)

Open the official site 本机内置 /translate/ in your usual browser and register an account (use your own email or phone number).
Complete business/identity verification on the site; if you don't have a business entity yet, applying as an individual is fine too.
Create an app/project in the site's dashboard and obtain the API key. Keep the key only on your computer; don't send it to anyone and never enter it into this system.
Come back here and press 'Key Ready' as a progress marker only; configuration is done hands-on on your computer during a remote session — the key never enters the database and never travels through a web page.
After configuration, run one small real call in the staging environment, keep a screenshot as evidence; it only counts as connected after your approval.

Information checklist to prepare

No signup; reuse the built-in /translate/ translation layer
Business or personal ID documents (for verification)
An online payment method (credit card or business bank account)
One active email address (for verification mail and billing)

Acceptance criteria after connecting

Run 1 real call in staging with the real key and keep a screenshot → boss reviews → only after Human-Gate approval does the status change from 'Simulated' to 'Connected'. Until then the page always shows simulation.

⚠ Real connection & switch-over are high-risk actions and always go through Human-Gate.

I have applied Key is ready

Buttons only mark progress; they perform no real action. Never enter key material into the system.