Jevmoji — amscotti

Yes. The key is supplied through the TYPESAFE_API_KEY environment variable or a .env file in the working directory or next to the binary, with the environment taking precedence. Without a key the page still serves, but /api/reactions answers 502 with a hint to check the key.

It is an example integration of the Jev API: one state plus one Noul question per emoji, evaluated together in a single POST /v1/systemone call. The internal/jev package is a typed TypeSafe System One client handling Noul, choice, and score answers.

The catalog holds 200 everyday and playful emojis, each with its own Noul question. It covers greetings, appreciation, celebrations, everyday emotions, work, food, and playful reactions, and all 200 are scored in one Jev call.

The strongest four reactions can qualify at 50% or higher, and a fifth appears only if its score reaches 75%. The scores are Jev's estimated probabilities that each emoji fits the message, and they are visible on hover or keyboard focus.

Yes. The same container deploys with gcloud run deploy --source=. --region=us-central1 --allow-unauthenticated, storing the key in Secret Manager and granting the runtime service account secretAccessor. Scale-to-zero means an idle demo costs nothing beyond the always-free allowance.

It is written in Go 1.27.1 with golangci-lint 2.14.0 and released under the MIT license. The multi-stage Dockerfile compiles a static, stripped Linux executable into a scratch image with the HTTPS CA bundle, running as a non-root user with HTML, CSS, and JavaScript embedded.