Skip to main content

ValiFit Constitutional Charter

Lead-Routing Neutrality

The principle

No agent receives better leads, higher fit scores, or preferential placement because they paid more. Routing is determined exclusively by Agent Quality Score (AQS).

The commitment

RESPA + FTC + state broker laws prohibit pay-to-play in lead distribution. ValiFit's connect-agent endpoint orders candidate agents by aqs_score DESC + agent_id ASC — never by subscription tier, credit balance, Stripe customer ID, or paid placement signal. AQS is computed from connection-lifecycle data only: response rate, acceptance rate, follow-through rate, with cohort-adjusted reliability and exponential time decay. Subscription tier gates FEATURE access (CRM, advanced market intelligence) but never RANKING. Capacity gating (you can't charge what the agent doesn't have) is BILLING, not RANKING.

Why this matters

When agents pay for better placement, buyers get matched to whoever paid most — not whoever best fits their needs. That's bad for buyers (worse outcomes) and bad for the platform (corrupted feedback signal). We make payment invisible to the routing engine and we lock that with a CI test.

How we enforce

__tests__/monetization-firewall.test.ts (10 tests, Phase 6.N) static-scans 9 scoring paths + ORDER BY clauses on /api/match/connect-agent for pay-to-play tokens (subscription_tier, paid_amount, stripe, credit_balance, premium_tier, sponsor, paying_agent, priority_interest). Allowlists wallet/pricing/integrations as billing surfaces.

Aligns with

  • RESPA 12 CFR 1024
  • FTC Section 5 (Unfair/Deceptive)
  • NAR Code of Ethics Article 6

Last reviewed and affirmed: 2026-05-08. The charter is versioned with the codebase — a Git history of changes to lib/charters.ts serves as the audit log.

Other charters