Official cep.is Telegram bot - @cepisbot http://git.cep.is/telegram/atom?h=v0.2.1 2026-07-27T23:46:40Z 2026-07-27T23:46:40Z Murilo Ijanc murilo@ijanc.org 2026-07-27T23:46:40Z urn:sha1:83ce95cf10fd9e9d581362453c558239d37ae06e Answering only "não encontrei" wastes the trip. A CEP that fails is almost never a random number: it is someone who knows the city and guessed the rest, most often at the "-000" that 957 municipalities never received. The API now names that municipality on the 404, so the reply names it too. It stays an answer to a failure. No 📮, no address block, and no CEP suggested from inside the range — the range is sparse (Areal's 118 CEPs span nearly five thousand numbers), so the reply gives the count and says so instead of letting the two ends read as a list of valid CEPs. cep.is/go v0.1.0 discards the 404 body, so internal/lookup reads it with one extra GET, on that path alone and never inside a retry. Everything that can go wrong there — a slow answer, broken JSON, a faixa naming no municipality — falls back to the reply the bot has always given. The wrapper goes away the day the library exposes the field. 2026-07-26T18:18:21Z Murilo Ijanc murilo@ijanc.org 2026-07-26T18:18:21Z urn:sha1:3ca1d2c4370e8e79aba3940d5c8fe115960b75a8