Use cases
Matrimonial and dating
Three independent compatibility systems computed on the same two charts, with disagreements surfaced rather than blended into one number. That is what beats a generic horoscope API here: not a bigger score, a more honest one.
| Product | Tool chain | Constraint |
|---|---|---|
| Match score on every profile card | run_kundli_match_complete, or expanded: get_ashta_koota_milan, check_compatibility, get_compatibility_advanced | Never present a low score as a reason a relationship will fail |
| The dosha filter users actually search on | check_doshas, get_kalsarpa_variants, run_pre_verdict_audit | Names which of 12 variants applies, and carries the KP dissent. Never a disqualifier |
| Partner-description prefill for search facets | analyze_natal_promise, get_spouse_characteristics, get_upapada_lagna | Suggestions, always editable |
| When is marriage likely | set_birth_profile, analyze_natal_promise, get_significators, get_ruling_planets, get_fruitful_significators, find_event_timing_v2, get_transit_timing_hierarchy, get_marriage_delay | Windows, never single dates as certainties |
| Second-marriage counselling lane | analyze_natal_promise, get_marriage_advanced, get_event_dasha | Advisor-facing only |
| Separation-risk screening | get_marital_separation, get_extramarital_signature | B2B advisor-only. Never consumer-facing, never about a third party |
| Chemistry card with no birth time | get_nakshatra_details, get_chara_karakas, get_arudha_lagna, get_ayurvedic_constitution | Entertainment framing |
| Wedding date both families accept | get_election_catalog, find_wedding_muhurta, find_joint_election_window, rank_candidate_dates | The two-chart mode is a Lumin extension, label it |
Separation-risk screening is advisor-only
Row 6 uses get_marital_separation and get_extramarital_signature. Both belong on the list of tools that must never reach a consumer surface. See responsible use.
Why it beats a generic horoscope API
Three independent compatibility systems computed on the same two charts, with disagreements surfaced rather than blended into one number.
Where to next
- kundli-match is the worked example for rows 1 to 3: three systems, side by side.
- Scheduling and electional for more on the joint-election pattern behind row 8.
- Responsible use for the matching disclaimer and the advisor-only tool list.