api · sample response

One puzzle, as the game receives it.

Each time you press New Puzzle, the game fetches /api/puzzle and gets a fresh puzzle with a unique solution. The API serves only the game itself, so here is one response, saved, with what each field means.

GET /api/puzzle200 · application/json
{
  "metrics": {
    "counts": {
      "blanks": 52,
      "clues": 29
    }
  },
  "puzzle": "4.9...6.....6.9.152...487...1......6.4..5..8.7......3...896...713.7.5.....7...8.1",
  "ref": "NDU5MTczNjI4ODczNjI5NDE1MjYxNTQ4NzkzMzEyODk0NTc2OTQ2MzU3MTgyNzg1MjE2OTM0NTI4OTYxMzQ3MTM0Nzg1MjY5Njk3NDMyODUx",
  "tag": "cloudflare"
}
fields
puzzle
81 characters, row by row from the top left. Digits are clues and dots are blanks.
ref
The solution as 81 digits, base64-encoded. The browser checks your entries against it, so Check needs no second request.
metrics.counts
How many cells are blank and how many are clues. The two always add up to 81.
tag
The platform that served the response: "cloudflare".

The solution ships with the puzzle on purpose: it's a casual game, and base64 only hides the answer from a glance. A request that doesn't come from the game page, such as a browser tab, another site or curl, gets a 404.