RPR
A property and valuation data vendor, integrated at the connector layer.
RPR supplies property and valuation records. The integration exists as connector evidence, which means the transport was written and the vendor sits under Connection without a product contract above it in the recorded sources.
Property records reached this way are a different acquisition path from the county pipeline documented under Data, which reads the jurisdiction's own record surface directly rather than a vendor's aggregation of it.
Products it serves
How this integration is built
- connection configuration
- The wire protocol. One repository per vendor API call, not per vendor.
- language configuration
- The field mapping between the vendor's vocabulary and the canonical model.
- flow file
- The four-way translation: canonical request, vendor request, vendor response, canonical response.
- waterfall priority
- One line naming where this vendor sits in the vertical's ordering.
- status call
- Activating the vendor for a lender, optionally with the lender's own credentials.
Evidence
This vendor is on the roster because each of the following resolves to a committed artifact.
bot-coborrower-previous-residency-collectorbot-coborrower-previous_employment-collectordata-manager-proxy-examplerpr-avm-extraction