G

Google Cloud Translation emulator

admin — changes apply immediately, defaults come from config

API keys

Allow-list of API keys accepted via `x-goog-api-key` or `?key=`. A key not on the list gets Google's 400 API_KEY_INVALID body; no key at all gets 403 CREDENTIALS_MISSING.

Fault injection

Injected latency (ms) before every call; force-failure answers every call with the documented Google error body for that status (400/403/429/500/503) until cleared.

Recent translations

Latest translate/detect calls — output is `[<target>] <text>` unless the config override map matched.

Requests from the backend

Danger zone

wipes payments, logs and every runtime override — back to configured defaults