Use cases
Commerce and personalization
Two sections, one shape: read the chart once, drive a catalog, a segment, or a send-time decision from it. The B2B section (O) is the same tool chains offered as infrastructure for someone else's product, rather than a feature in your own.
E-commerce and D2C personalization
| Product | Tool chain | Constraint |
|---|---|---|
| Onboarding profile that drives the catalog | get_full_chart, get_nakshatra_details, get_arudha_lagna, get_chara_karakas, get_shadbala, get_d2_chart | Entertainment framing |
| Gift finder keyed to the recipient | get_nakshatra_details, get_yoga_karaka, get_ishta_devata, get_gemstone_recommendation | Decorative, no fortune claims |
| Festival and auspicious-day merchandising | get_panchang, get_choghadiya_today, get_hora_today, get_tara_bala | None |
| Launch and drop timing | get_election_catalog, find_business_launch_time, rank_candidate_dates, find_meeting_time | Internal planning, not a sales promise |
| Loyalty tier keyed to a personal cycle | get_smart_current_dasha, get_annual_forecast, get_saturn_return, get_jupiter_return | None |
| Colour, metal and material palette | get_yoga_karaka, get_gemstone_recommendation, get_ayurvedic_constitution | Aesthetic personalization |
| Send-time optimisation per user | get_moon_transit, get_sublord_changes, get_tara_bala | None |
Why it beats sun signs
Public image (get_arudha_lagna) and soul drive (get_chara_karakas) are two different axes from two different traditions. 27 birth-star buckets, not 12.
B2B SaaS personalization
| Product | Tool chain | Constraint |
|---|---|---|
| A personalization API for any consumer app | set_birth_profile, get_tool_catalog, then the routed plan | The consuming product owns its disclaimers |
| Segment builder for a CRM or CDP | get_ayurvedic_constitution, get_chara_karakas, get_yoga_karaka, get_shadbala, get_arudha_lagna | Birth data is personal data. Disclose it |
| Send-time optimisation as a service | get_moon_transit, get_sublord_changes, get_rp_interval, get_tara_bala | None |
| Data-quality service for an existing astrology product | get_boundary_warnings, get_subsub_boundary, check_rule_of_origin, run_pre_verdict_audit | None |
| Cross-system consensus as a confidence API | get_multi_system_verdict, get_kcil_verdict, get_four_step_verdict, run_triple_dasha_consensus | Label each school, never blend into one authority |
The one nobody else sells
The data-quality row is a service that tells an existing astrology database how much of it is unreliable, grounded in the fact that a six arc-minute shift can invert a verdict.
Where to next
- wellness-matcher and products-matcher are worked examples for the onboarding and gift-finder rows.
- Recipes for the composite-versus-expanded call-count tradeoff behind the personalization API row.