Skip to content मुख्य सामग्री
Free tools · No registration · Private by design
The Indian AstrologyAncient wisdom, precise calculations
A Pandit.com initiativePandit.com ↗
Historical audit archive

Vendor integration is retired.

This page preserves value-free evidence from systems being replaced. Every current and future calculation, interpretation and API contract is a first-party The Indian Astrology product.

11public forms proven to call AstrologyAPI v1
6public forms proven to stay inside local PHP
14unique legacy resource paths observed in production source
0vendor integrations or compatibility adapters planned
Native field-mapping evidence

Every consumed field now has an honest disposition.

Automated synthetic native runs proved that every declared native path existed when this archive was frozen. Candidate mappings are retained as history only; they do not define current formulas, fields or product priorities.

45source-observed legacy paths classified exactly once
10direct native candidates with verified paths
5derived candidates requiring a declared transform
30runtime-gated or intentionally without an equivalent

What path verification proves

The named field exists in a synthetic response from the same native engine selected by the observed public form. It prevents documentation drift and broken translation targets.

What it does not prove

It does not establish provider values, defaults, date formatting, array ordering or semantic equivalence. Those questions stay behind the authorized runtime-fixture and shadow-acceptance gate.

Public-form migration

Preserve the input. Upgrade the engine.

POST an observed form identifier and fields to the migration route. It derives an IANA timezone from lat/lang, ignores identity fields, and returns the authoritative TIA native envelope with an explicit non-compatibility boundary.

POST /api/v2/migrations/mahaguru/public-form
{
  "formIdentifier": "ascendant",
  "birthday": 1,
  "birthmonth": 1,
  "birthyear": 1990,
  "birthtime": 12,
  "birthminute": 0,
  "lat": 28.6139,
  "lang": 77.209,
  "timezone": 5.5,
  "language": "en",
  "referenceDate": "2026-09-10"
}
Inspect the OpenAPI contract
Public consumer evidence

Mahaguru form inventory

These public paths and form identifiers were observed directly on 11 September 2026. The migration route can now normalize all 17 into transparent native calculations, but it deliberately does not imitate the private provider response.

Public pathCalculatorForm identifierSurfaceEvidence
/ascendant-calculator/Ascendantascendantshared birth formform observed
/kaal-sarp-dosha-calculator/Kaal Sarp Doshakalsarpa_doshashared birth formform observed
/shani-sade-sati-calculator/Shani Sade Satisadhesatishared birth formform observed
/pitra-dosha-calculator/Pitra Doshapitradoshashared birth formform observed
/manglik-dosha-calculator/Manglik Doshamanglikdoshashared birth formform observed
/nakshatra-calculator/Nakshatranakshatrashared birth formform observed
/yogini-dasha-calculator/Yogini Dashayoginidashashared birth formform observed
/moon-sign-calculator/Moon Signmoonsignshared birth formform observed
/biorhythm-calculator/Biorhythmbiorhythmshared birth formform observed
/atmakaraka-calculator/Atmakarakaatmakarakashared birth formform observed
/ishta-devata-calculator/Ishta Devataishatdevtashared birth formform observed
/lucky-bracelet-calculator/Lucky Braceletluckybracelateshared birth formform observed
/lucky-rudraksha-calculator/Lucky Rudrakshaluckyrudrakshashared birth formform observed
/unlucky-date-calculator/Unlucky Dateunluckydateshared birth formform observed
/lucky-date-calculator/Lucky Dateluckydateshared birth formform observed
/numerology-lucky-colour-calculator/Lucky Colourluckycolourshared birth formform observed
/lucky-vehicle-number-calculator/Lucky Vehicle Numbervehicle-numberpage-local formform observed
Production source evidence

Eleven call the provider. Six stay local.

A credential-free, visitor-log-free audit of the active AstroNumero 1.0.1 handler identified the exact execution split. Source fingerprints are published in the JSON manifest; source code and secrets are not.

14 observed v1 resources

  • general_ascendant_report
  • kalsarpa_details
  • sadhesati_life_details
  • sadhesati_current_status
  • pitra_dosha_report
  • manglik
  • general_rashi_report/moon
  • general_nakshatra_report
  • planets
  • current_yogini_dasha
  • major_yogini_dasha
  • biorhythm
  • jaimini_details
  • isht_devata

Six local-only handlers

  • luckybracelate
  • luckyrudraksha
  • unluckydate
  • luckydate
  • luckycolour
  • vehicle-number
Broader private-source inventory

Two systems called Mahaguru—now kept separate.

The active WordPress calculators above use AstroNumero and AstrologyAPI. A separate private Mahaguru repository contains a newer native API surface. Its frozen source index is useful migration evidence, but it is not proof of live traffic, calculation validity or endpoint parity.

200unique routes in the synthetic source index
97anonymous core candidates; no parity implied
77protected or API-keyed operations deferred
10endpoint wrappers in the recorded web client
Source familyAnonymous operationsTIA authorityEvidence status
ashtakvarga2kundli-and-doshasubject overlap only
aspects3kundli-and-doshasubject overlap only
astrology10kundli-and-doshasubject overlap only
btr2classical-workbenchsubject overlap only
dashamsha2kundli-and-doshasubject overlap only
dosha-yoga4kundli-and-doshasubject overlap only
doshas3kundli-and-doshasubject overlap only
dwadashamsha2kundli-and-doshasubject overlap only
festivals5panchang-and-calendarsubject overlap only
horoscope4predictionssubject overlap only
kundli3kundli-and-doshasubject overlap only
matching9match-makingsubject overlap only
muhurat8muhuratsubject overlap only
navamsa2kundli-and-doshasubject overlap only
numerology2numerologysubject overlap only
panchang14panchang-and-calendarsubject overlap only
rudraksha3review-only-recommendationssubject overlap only
sade-sati2kundli-and-doshasubject overlap only
saptamsha2kundli-and-doshasubject overlap only
transit3predictionssubject overlap only
varshaphal2kundli-and-doshasubject overlap only
vastu5vastu-and-directionsubject overlap only
yogas3kundli-and-doshasubject overlap only
yogas-auspicious2muhuratsubject overlap only

Validation stays honest

The source plugin manifest marks 0 calculation plugins as validated. Route presence and a successful synthetic response therefore cannot become formula authority.

Two count gaps retained

The narrative says 202 routes while its route index contains 200. The partial Vrat plugin also declares 5 patterns absent from that index. Both remain review gates.

Inspect the value-free source manifest
Response contract evidence

The fields in use are now visible.

Only field paths and data types are recorded—never sample interpretation text. This clean-room comparison shows what Mahaguru reads, what the current official samples structurally expose, and where runtime fixtures are still indispensable.

13resources with current official structural samples
1resource documented only by production source
1documented root-shape conflict requiring a runtime fixture
0legacy adapters published or planned

Biorhythm: stop and verify

The current official sample is a JSON string, but the production handler dereferences physical, emotional, intellectual and average objects. An actual redacted runtime response is required before translation code is safe.

Ishta Devata: source only

The active handler calls isht_devata and reads devata_name plus report, but no current public reference page was found. TIA will not invent the missing contract or copy provider prose.

Offline evidence tool

Capture shape. Discard every value.

The maintainer-only capture command reads an explicitly authorized synthetic JSON response from standard input. It emits registered paths, types, consumed-field coverage and a SHA-256 shape fingerprint. Scalar values and array indexes are discarded; unknown keys become a generic review sentinel. No credential or network request is accepted.

cd api
uv run tia-capture-legacy-contract \
  --resource biorhythm \
  --kind success \
  < authorized-synthetic-response.json
Outgoing request evidence

The outgoing request is now traced.

A value-free source audit records the exact provider payload shape used by the 14 observed resources. It publishes field origins and missing defaults—not credentials, visitor values or the client's private placeholder text.

Nine provider fields

  • day · month · year · hour · min · lat · lonvisitor-derived calculation values
  • tzonereturned by a separate timezone lookup with isDst=false
  • namea static client placeholder; the visitor name is not forwarded and the literal remains unpublished

Defaults still unverified

  • The form language is not forwarded; the public handler makes zero setLanguage calls and sends no Accept-Language header.
  • No ayanamsha field is transmitted, so the effective provider/account default remains unverified.
  • This documents old source behavior; it is not a pattern for the native API to copy.
Current documentation comparison

The current guide and the legacy client have drifted.

Current official guidance documents eight required birth fields and date-aware timezone_with_dst resolution. The active legacy client adds a static name field and uses the older timezone request. Treating those contracts as identical would hide a calculation risk.

8fields in the current documented shared birth payload
9fields observed in the active legacy calculation payload
1legacy-only static name field, with its value unpublished
0provider calls made for this comparison

timezone_with_dst

The current guide resolves tzone from latitude, longitude and the birth date. Date-sensitive DST is part of the documented calculation path.

Why the old study stopped

Public documentation could not prove exact account response shapes, defaults or historical behaviour. Rather than imitate an uncertain contract, the product direction now builds independent native outputs.

Retained audit tool

Historical evidence, not a product dependency.

The maintainer-only comparison command is retained to reproduce past audit records. It has no HTTP client, credential option or public endpoint and cannot authorize integration, compatibility work or native formulas.

cd api
uv run tia-compare-legacy-shadow \
  < authorized-synthetic-comparison.json
Candidate matrix

What maps—and what does not

Documented endpointCategoryNative destinationStatusReason
/v1/planetsBasic Astro/api/v2/calculations/kundlicandidateGraha fields overlap; consumer fixture required.
/v1/basic_panchangPanchang/api/v2/calculations/panchangcandidateTimezone and response-field translation must be compared.
/v1/current_vdashaVimshottari Dasha/api/v2/calculations/kundlicandidateDasha evidence exists; legacy nesting is not assumed.
/v1/kp_planetsKP Astrology/api/v2/calculations/kp-prashnanot-equivalentHorary KP is not a proven natal KP drop-in.
/v1/lalkitab_horoscopeLal Kitab/api/v2/calculations/lal-kitabcandidateIndependent fixed-house evidence; proprietary prose excluded.
/v1/match_ashtakoot_pointsMatch Making/api/v2/calculations/match-makingcandidateAuditable Ashtakoota exists; exception fields need fixtures.
/v1/numero_tableNumerology/api/v2/calculations/numerologycandidateIndependent numbers only; vendor interpretations are not copied.
/v1/sun_sign_prediction/daily/{sign}Horoscopes/api/v2/predictions/dailynot-equivalentVedic Moon-sign output cannot masquerade as Sun-sign output.

Retired product direction

  • No AstrologyAPI integration
  • No vendor-compatible response contract
  • No future adapter wave
  • Build missing products natively

Frozen boundaries

  • No proxy calls or vendor credentials
  • No proprietary interpretations copied
  • No /compat legacy routes published
  • Native API remains source of truth

Historical machine-readable register

This archive accepts no birth data and exists only to document the retired migration study. Native product APIs are authoritative.

JSON archive ↗Back to native API

Page method and limits पृष्ठ विधि और सीमाएँ

Historical migration evidence: method, evidence and limits

A non-product audit archive documenting old dependency surfaces that independent The Indian Astrology products replace.

स्वतंत्र The Indian Astrology उत्पादों द्वारा बदले गए पुराने dependency surfaces का गैर-उत्पाद ऑडिट संग्रह।

01

How it works / कार्यविधि

Value-free historical inventories are retained for clean-room audit only; they do not define formulas or native API contracts.

मान-रहित ऐतिहासिक सूचियाँ केवल clean-room audit के लिए रखी गई हैं; वे formulas या native API contracts निर्धारित नहीं करतीं।

02

Evidence standard / प्रमाण मानक

This route links only to registered source and comparison records. Keep the input summary, engine version, calculation version and intermediate values with the result.

यह route केवल दर्ज source और comparison records से जुड़ता है। परिणाम के साथ input summary, engine version, calculation version और मध्यवर्ती मान सुरक्षित रखें।

03

Limits / सीमाएँ

Vendor integration, proxying, compatibility adapters and cloned response contracts are retired and not planned.

Vendor integration, proxying, compatibility adapters और cloned response contracts समाप्त हैं और नियोजित नहीं हैं।

Route evidence

Sources and contextual next steps / स्रोत और अगला चरण

The organization maintains the page text and route evidence. Versioned software profiles and tests—not a personal byline—establish numerical reproducibility.

संगठन पृष्ठ सामग्री और route evidence बनाए रखता है। संख्यात्मक पुनरुत्पादकता व्यक्तिगत नाम से नहीं, संस्करणबद्ध software profile और tests से स्थापित होती है।

Questions answered on this page

Frequently asked questions / सामान्य प्रश्न

What does the Historical migration evidence page establish? / ऐतिहासिक माइग्रेशन प्रमाण पृष्ठ क्या स्पष्ट करता है?

A non-product audit archive documenting old dependency surfaces that independent The Indian Astrology products replace. Value-free historical inventories are retained for clean-room audit only; they do not define formulas or native API contracts.

स्वतंत्र The Indian Astrology उत्पादों द्वारा बदले गए पुराने dependency surfaces का गैर-उत्पाद ऑडिट संग्रह। मान-रहित ऐतिहासिक सूचियाँ केवल clean-room audit के लिए रखी गई हैं; वे formulas या native API contracts निर्धारित नहीं करतीं।

What is outside this page's scope? / इस पृष्ठ के कार्यक्षेत्र से बाहर क्या है?

Vendor integration, proxying, compatibility adapters and cloned response contracts are retired and not planned.

Vendor integration, proxying, compatibility adapters और cloned response contracts समाप्त हैं और नियोजित नहीं हैं।

Published by The Indian Astrology editorial teamContent modified · Evidence reviewed Source register and provenance →Review licensing and source status →