Bilateral Match Percentage

Source

ValiFit Internal Compute · vintage 2026 · refresh cadence: live

The bilateral match% from Atlas Invariant 1 — same % shown to both sides of a dyad

Direction of better

Higher values are better. Used to rank candidate towns/properties; higher score = stronger fit.

Unit

Values are reported in percent.

Where the data lives

Tables: lead_assignments

Columns: match_pct

Input field: match_pct

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": "match.bilateral_pct",
  "name": "Bilateral Match Percentage",
  "value": 12.4,
  "unitText": "percent",
  "additionalProperty": [
    {
      "@type": "PropertyValue",
      "name": "composite",
      "value": "Match_Score"
    },
    {
      "@type": "PropertyValue",
      "name": "level",
      "value": "address"
    },
    {
      "@type": "PropertyValue",
      "name": "direction",
      "value": "higher_better"
    },
    {
      "@type": "PropertyValue",
      "name": "source_year",
      "value": "2026"
    },
    {
      "@type": "PropertyValue",
      "name": "fha_safe",
      "value": true
    }
  ],
  "valueReference": {
    "@type": "QuantitativeValue",
    "additionalType": "https://valifit.com/catalog/metric",
    "identifier": "match.bilateral_pct",
    "sameAs": "ValiFit Internal Compute"
  },
  "mentions": [
    {
      "@type": "Dataset",
      "@id": "https://valifit.com/sources/valifit-internal",
      "identifier": "VALIFIT_INTERNAL",
      "name": "ValiFit Internal Compute",
      "url": "https://valifit.com/trust/methodology",
      "sameAs": "https://valifit.com/trust/methodology",
      "creator": {
        "@type": "Organization",
        "name": "ValiFit"
      },
      "temporalCoverage": "live",
      "dateModified": "2026-05-11"
    }
  ]
}