Source
User input · vintage 2026 · refresh cadence: live
minimal / standard / strict / institutional — affects match-rate with renters
Direction of better
No universal direction; user preference determines what is "better".
Unit
Values are reported in category.
Default weight in Landlord composite
5% of the Landlord composite by default. Users can override this weight in their intake; the displayed score reflects the user's chosen weighting, never a fixed default.
Where the data lives
Tables: user_intake
Columns: screening_strict
Input field: screening_strict
JSON-LD example
Every value emitted by ValiFit (in /api/v1, MCP responses, on-page JSON-LD) carries a propertyID set to this metric_id, so AI clients can resolve it back here in one round-trip.
{
"@type": "PropertyValue",
"propertyID": "landlord.tenant_screening_strict",
"name": "Tenant Screening Strictness",
"value": "example",
"unitText": "category",
"additionalProperty": [
{
"@type": "PropertyValue",
"name": "composite",
"value": "Landlord"
},
{
"@type": "PropertyValue",
"name": "level",
"value": "user"
},
{
"@type": "PropertyValue",
"name": "direction",
"value": "optimize"
},
{
"@type": "PropertyValue",
"name": "source_year",
"value": "2026"
},
{
"@type": "PropertyValue",
"name": "fha_safe",
"value": true
}
],
"valueReference": {
"@type": "QuantitativeValue",
"additionalType": "https://valifit.com/catalog/metric",
"identifier": "landlord.tenant_screening_strict",
"sameAs": "User input"
},
"mentions": [
{
"@type": "Dataset",
"@id": "https://valifit.com/sources/user-input",
"identifier": "USER_INPUT",
"name": "User Input",
"url": "https://valifit.com/intake",
"sameAs": "https://valifit.com/intake",
"creator": {
"@type": "Organization",
"name": "ValiFit user"
},
"temporalCoverage": "live",
"dateModified": "2026-05-11"
}
]
}For programmatic access
GET /api/v1/catalog/metrics?id=landlord.tenant_screening_strict
MCP tool: get_catalog with id="landlord.tenant_screening_strict"