Multilateral Development Bank Procurement Monitor
Pricing
from $1.00 / 1,000 world bank procurement notices
Extracts the World Bank's public Procurement Notices API and its 'Other Sanctions' debarment sub-table, normalized to the fleet's 18-field UMS. ADB (Cloudflare-gated) and IDB (Power BI-only, CKAN API robots.txt-blocked) were live-researched and honestly deferred, not force-scraped - see README.md.
src/fingerprint.ts computes a dual hash pair per notice (statusFingerprint over notice_status - the real status field this source provides - and contentFingerprint over its other mutable fields). src/delta.ts's classifyProcNotice() computes NEW_LISTING (first-seen, name preserved from v1) / STATUS_CHANGE / UPDATED / SNAPSHOT_NO_DIFF.src/state.ts rewritten to a { entries: Record<source, Record<id, {statusFingerprint, contentFingerprint, lastSeenAt}>>, lastRunAt } shape (was { seenIds: Record<source, string[]>, lastRunAt }). Named Actor.openKeyValueStore() was already correct here - no store-migration risk.is_new is now always populated (true/false), not only when onlyNew is enabled.src/http.ts's retry logic to be explicitly 429/5xx-calibrated (was: retry on any non-ok status, including permanent 4xx like 400/404 - wasteful but not incorrect, since a genuinely non-retryable error still eventually surfaced after burning through its retry budget). Now distinguishes retryable (429/5xx) from non-retryable (other 4xx) explicitly, adds exponential backoff + jitter, and honors a real Retry-After header when present - matching the fix made the same day to a sibling actor (actor-22-drug-safety-recalls-monitor), covered by 5 new tests mocking real 429/503/404 scenarios.src/dateUtils.ts's isWithinDateRange: added the diffMs >= 0 guard already proven necessary elsewhere in this fleet (a naive one-sided check lets a future-dated value match every window). Not a live-observed bug here (this actor only applies it to noticedate, a retrospective publish date) but fixed proactively.LICENSE (Apache-2.0, matching the fleet standard), .github/workflows/test.yaml (lint+build+test CI - this actor had none), CHANGELOG.md, AGENTS.md.test/fingerprint.test.ts, test/delta.test.ts, test/state.test.ts, test/http.test.ts: unit coverage of the new classification/fingerprint/state-persistence/retry logic - previously the actual delta logic (a flat seenIds check) had zero dedicated tests, only the pure UMS-mapping layer was tested.onlyNew: now means "new or changed since last run" (delivers STATUS_CHANGE/UPDATED too), not just "never seen before" - matching the same upgrade made the same day to actor-22-drug-safety-recalls-monitor and actor-19-maritime-sanctions-monitor in this fleet.is_new: null, event_type: 'SANCTION' always, correctly matching this fleet's convention for a source with no delta-tracking concept (a small static snapshot page, not a paginated/dated feed). This was already correct in v1 and did not need fixing.CLOSED event on the procurement-notices sub-source. Unlike actor-19-maritime-sanctions-monitor's OFAC SDN feed (a single-file, guaranteed-complete export), the World Bank Procurement Notices endpoint is genuinely server-side paginated and the fetch loop stops once maxItemsPerSource is reached - a fetch here is not reliably a complete census the way OFAC's is. There is also no independently live-verified evidence this endpoint ever removes a notice from its result set rather than updating its notice_status in place (which IS captured as a real STATUS_CHANGE here). Adding a CLOSED-by-absence check without that verification would risk the exact false-positive class of bug already found and fixed on this fleet's entrerios-compras-monitor and salta-compras-monitor.maxItemsPerSource cap combined with real state persistence already avoids re-processing already-known notices across runs.GET acts/{id} before this release shipped: the two-tier pricing (procurementNotices $0.001/record, debarredFirms $0.003/record) matches the code's documented intent exactly and is untouched by this release.