land_deeds_search

Search public land deeds by player or place (tract_id or region_number); a bare search is refused. A successful limited response is {status, data}, where data is an object carrying deeds, worksite_details and staking_details arrays. The catalogue declares those arrays as arrays of objects, and declares deed_uid as a string ID on each row; use that common deed_uid to join the three arrays. The deeds rows carry the public land-deed fields declared for this route. The worksite_details and staking_details rows carry the fields declared for those arrays, including staking_details[].total_work_per_hour, the per-deed total that a caller would rank deeds by; the response also carries a separate per-hour rate, worksite_details[].work_per_hour_per_one_pp, and this server does not relate the two; what it counts is not stated by the response and is not claimed here. total_work_per_hour is a JSON number, not a string, and this server returns it unchanged; it does not convert, round, rank, sort, sum or compare it, and a change in that wire type would be reported as a malformed response rather than converted silently. A zero total_work_per_hour was observed on deeds whose is_powered value was false, on one page of one account on one day (library/observations/land-deeds-search-details-2026-09-07.md); that observation does not establish that zero proves a deed is unpowered, what the figure counts beyond the field name, or what any unobserved value means. An empty result is a successful upstream answer, not an error, and establishes only that this response carried no rows; it does not establish that an account, place or deed does not exist, that no other matches exist, or that the response is complete. The limited form of this search has object-shaped data rather than an array, so this server's 100-row bound does not apply to that response. The only server result bound that applies to that response is the 256 KB serialized-result limit, and that limit is all-or-nothing. An oversized limited response returns status alone with the deeds, worksite_details and staking_details arrays dropped; the text says "This single record is too large to return within the 256 KB result limit." Request a smaller limit; retrying the same call will not return partial data. Paging probes recorded for this route were offset=0, offset=5, limit=10000, three calls omitting all parameters, and orderBy=desc: offset=0 returned zero rows; offset=5 returned the first four rows of the omitted-offset response; limit=10000 returned 10000 rows; the three omitted-parameter calls returned zero bytes; and orderBy=desc returned an empty data array. No total or has-more field was observed. No offset value tried reached later rows than the omitted-offset response; narrow the player, tract_id or region_number request instead. The observed ordered probe with orderBy=desc returned an empty array (measured 2026-09-06), and this server's contract currently accepts that response. A non-empty ordered response would be reported as malformed rather than returned. Because the observed ordered response was empty, no row bound or truncation is described for that form. Paging probes recorded for this route were offset=0, offset=5, limit=10000, three calls omitting all parameters, and orderBy=desc: offset=0 returned zero rows; offset=5 returned the first four rows of the omitted-offset response; limit=10000 returned 10000 rows; the three omitted-parameter calls returned zero bytes; and orderBy=desc returned an empty data array. No total or has-more field was observed. No offset value tried reached later rows than the omitted-offset response; narrow the player, tract_id or region_number request instead. This server makes one logical upstream request and reports what that request returned; it does not claim to analyse, rank, sort, sum or compare the returned deeds or detail rows.