pet.trezy.getFeatureStatus
The caller's own Pet of the Week state: consent, the account-wide interaction count, this week's pick and the last posted feature. ⚠ IT ONLY EVER DESCRIBES THE CALLER; there is no parameter that names anybody else.
Details · query
| Kind | query |
|---|---|
| Authority | trezy.pet |
| Indexed |
Query
query · GETOutput
application/jsonconsenting
booleanerror
stringknownValues: not-authenticated
interactions
integerAccount-wide, not per pet.
minimum: 0
lastPosted
refmessage
string#current
objectProperties
petName
stringAbsent when the pet's name can't be read — its trezy_pet_pets row is missing or hasn't caught up with the feature record yet. Requiring it would fail response validation and turn a valid answer into a 500 on that lag.
maxLength: 8
#posted
objectSimilar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
pet.trezy.getFeatures
queryFeature records, newest week first, with what a reader needs to show them: the pet's facts, the keeper's reply and consent. Public: every field here is already public in somebody's repo.
-
Keepers who could be Pet of the Week as of a moment, and for each the pets that could be featured. A keeper qualifies when they have a featureConsent record, an activity record in the 14 days before asOf, no refused record in the 90 days before it, were not the keeper of a feature picked in the 365 days before it, and were not passed over in the 84 days before it. A pet qualifies when it is not retired and has at least 3 interactions. Every window is measured from asOf, never from the clock, so
-
pet.trezy.feature
recordOne week's Pet of the Week, held in the publisher's repo. The record key is the ISO week (e.g. 2026-W39), so there is exactly one per week and every step that writes it is idempotent. ⚠ ONLY THE PUBLISHER'S COPY COUNTS. The index refuses this collection from any other repo, because eligibility, the ribbon and the badge all read it.