List DICT poll feed states
Reports which DICT poll feeds (claim discovery, MED infraction/refund discovery, the fraud-marker inventory sweep, funds-recovery event notifications) are frozen on a durable blocked marker, with the closed-vocabulary reason and the instant the freeze started. It also reports the funds-recovery feed’s replay list: BACEN records it permanently stepped over and never stored, named by BACEN resource id, which are replayed through POST /api/v1/dict/funds-recoveries/intake. It also names the records a feed is currently stuck on and the ones a named operator has permanently abandoned: a held record listed here is the id an operator supplies to POST /api/v1/dict/discovery-feeds//abandon-record, which is how a walk pinned on a record this deployment can never store is made to move on. A frozen feed deliberately does NOT degrade readiness — this rail also serves Pix keys, entries and claims, and the routes an operator needs to resolve a freeze are served by the same replicas — so this route, the brspi_dict_feed_blocked gauge and the operational event are the alarm.
Authorizations
JWT bearer token issued by the identity provider.
Response
OK
State of every DICT poll feed that can freeze.
How many regulated records named operators have abandoned across all listed feeds. Permanent.
0
How many of the listed feeds are currently frozen.
0
How many of the listed feeds are running but not covering everything — pinned on a record this deployment permanently refuses, on an entry whose BACEN resource id could not be read, or (the fraud-marker sweep) on a window left edge that stopped advancing. Each one names what it is stuck on in heldBacenRecordIds.
0
Every DICT poll feed that can freeze, blocked or not.
How many of the listed feeds carry BACEN records they permanently stepped over and never stored, awaiting replay.
0

