Blog
Vastu API: automated Vastu Shastra floor plan analysis
· 96Astro API team · 7 min read · Guides

How a Vastu API scores a floor plan by the 16 zones, 45 devatas, marma points and entrance padas, with examples, honest scoring and ideas for property apps.
In brief
- A Vastu API scores a floor plan by the rules of Vastu Shastra: the 16 zones, the 45 devatas of the Vastu Purusha Mandala, the marma points and the entrance padas.
- With the 96Astro Vastu API you send a plan as room coordinates, a DXF file or a photo of the plan, and get an overall score, the defects with their remedies, a heatmap by life area and comparisons between layouts.
- It is built for property portals, home-buyer reports, interior designers and Vastu consultants.
- The score is transparent: it says how many checks it could assess and what was missing, instead of hiding a guess behind a number.
Vastu Shastra is one of the first things many Indian home buyers ask about: is the kitchen in the south-east, where is the main entrance, which way does the bed face? A Vastu API lets property websites, design tools and consultants answer those questions automatically and consistently. This guide explains how a Vastu floor plan analysis works, what the 96Astro Vastu API returns, and how to build Vastu features into a property product.
What Vastu floor plan analysis checks
Traditional Vastu divides a site into directional zones and a grid of padas (squares) ruled by deities. An automated analysis does the same geometry on a plan:
| Concept | What it is | What the API does |
|---|---|---|
| 16 zones | The directions from the centre: N, NNE, NE, ENE, E and so on | Works out which zones each room falls in, by floor area |
| Vastu Purusha Mandala | The 81-pada (9×9) grid with 45 devatas | Maps the plan onto the grid and names the devata of each area |
| Marma points | Sensitive points of the mandala that should be kept clear | Checks for toilets, stairs, entrances, structures or walls on them |
| Entrance padas | The 32 entrance positions around the four sides | Reads the main door's pada and its traditional effect |
| Brahmasthan | The centre of the plan | Checks whether it is kept open |
| Ayadi | Dimension rules connecting a building's size to its owner | Calculates Aaya-Vyaya, Yoni, Nakshatra and Vara |
The rules are applied room by room: a kitchen is assessed against the zones favoured for fire, a master bedroom against the south-west, a pooja room against the north-east, and so on.
The Vastu API endpoints
| Capability | What it does |
|---|---|
vastu-analyse | The full floor analysis: overall score, defects, remedies, zones and devatas |
vastu-heatmap | Scores across the plan for one life area (such as career, wealth or marriage) for a visual heatmap |
vastu-compare | Compares two plans or two orientations side by side |
vastu-room-placement | Reads one room's placement |
vastu-entrance-pada | The main entrance's pada and its effect |
vastu-pada-grid | The 81-pada grid with its devatas, to draw over a plan |
vastu-ayadi | Ayadi calculations from the dimensions and the owner's nakshatra |
vastu-combined-with-city | Combines a home's Vastu scores with a city's location-astrology scores |
vastu-auspicious-times | Good times to carry out remedies |
vastu-import-dxf | Reads a CAD (DXF) plan |
vastu-vision-detect | Reads the rooms from an image of a plan with a vision model |
vastu-explain-defect, vastu-rank-remedies | AI explanations of a defect and remedies ranked for a household |
vastu-templates, vastu-template, vastu-reference | Ready-made plans for demos and the reference tables |
A first Vastu analysis request
Describe the plot boundary and each room as polygons, and say where north is:
curl https://api.96astroapi.com/v1/vastu/vastu-analyse \
-H "Authorization: Bearer $ASTRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"units": "m",
"north": { "degrees": 0, "reference": "true" },
"boundary": [[0, 0], [12, 0], [12, 9], [0, 9]],
"rooms": [
{ "name": "Kitchen", "type": "kitchen", "polygon": [[9, 6], [12, 6], [12, 9], [9, 9]] },
{ "name": "Master bedroom", "type": "master_bedroom", "polygon": [[0, 5], [4, 5], [4, 9], [0, 9]] },
{ "name": "Pooja", "type": "pooja", "polygon": [[10, 0], [12, 0], [12, 2], [10, 2]] },
{ "name": "Entrance", "type": "main_entrance", "polygon": [[5, 0], [7, 0], [7, 1], [5, 1]] }
]
}'
Reading the Vastu score honestly
The score measures agreement with the selected traditional rules, not structural safety, building-code compliance or a proven likelihood of health, wealth or marriage outcomes. Keep professional building inspections separate.
A Vastu score is only as good as the plan behind it. If a plan has no toilet, the toilet checks cannot be assessed. Instead of quietly giving full marks, the response says so:
{
"overall_score": 61.0,
"score_status": "assessed",
"score_basis": {
"coverage_pct": 61.1,
"checks_assessed": 11,
"checks_not_assessed": 7,
"missing": ["a toilet or bathroom"],
"explanation": "Based on 61.1% of the automatic checks."
},
"defect_count": 2,
"severe_defect_count": 1
}
Show coverage_pct and missing next to the score. A buyer who sees "61 out of 100, based on 61% of the checks; add the bathrooms for a full score" trusts the number. A score with no explanation invites arguments with every consultant.
The response also documents how it scored (scoring_method): a room counts in the zone that holds most of its floor, parts under 15% of a room are left out, a part of 25% or more in a zone to avoid becomes its own defect, and larger rooms count for more without drowning small ones.
North: true north vs magnetic north
Getting north wrong rotates every result. The API asks whether your north reading is true or magnetic. A compass reading may be magnetic; phone apps can display either true or magnetic north. Check the device setting and stored reference before correcting it; the API can correct it for the local magnetic declination and reports the correction it applied, with an uncertainty in degrees. On a property portal, store the orientation with the listing and show it on the plan.
Three ways to get the plan in
- Coordinates. Best for property portals and design tools that already hold room geometry.
- DXF import.
vastu-import-dxfreads CAD drawings that architects already have. - A photo or scan.
vastu-vision-detectreads the rooms from an image of a plan with a vision model. Let the user correct the detected rooms before you analyse them: one wrongly labelled room changes the result.
Vastu features for property websites
- A Vastu badge on listings. "Vastu score 78, kitchen south-east, entrance north-east", with a link to the full report.
- A Vastu filter. Let buyers filter by entrance direction or by score, with the coverage shown.
- Compare two flats.
vastu-compareputs two layouts or two orientations side by side, which is exactly how buyers decide. - A downloadable Vastu report as a lead magnet: the buyer leaves a phone number, you send a branded PDF.
- Vastu plus location.
vastu-combined-with-cityblends the home's scores with the city's location astrology scores for career, wealth and marriage.
Vastu tools for consultants and designers
- The 81-pada grid over the client's plan, with the devata in each pada, for consultations.
- Entrance pada readings to discuss door placement.
- Ayadi calculations from the building's dimensions and the owner's nakshatra.
- Remedy timing.
vastu-auspicious-timesfinds good days to carry out remedies, from the panchang at the property's location. - AI explanations.
vastu-explain-defectexplains a defect in plain words, andvastu-rank-remediesranks remedies for a household, so a consultant's report reads well without hours of writing.
Practical advice
- Validate polygons. Rooms should sit inside the boundary and not overlap; reject a plan early rather than score nonsense.
- Label room types carefully. The rules depend on the type:
kitchen,master_bedroom,pooja,main_entrance, toilets and stairs. - Show remedies as suggestions, not orders. Most families will not move a kitchen; a good report offers practical alternatives.
- Keep the version. The response includes the scoring method's version, so a later recalculation can be explained.
Frequently asked questions
What is a Vastu API?
It is an API that analyses a floor plan by the rules of Vastu Shastra and returns a score, defects, remedies, zones and devatas, so apps can offer Vastu checks automatically.
Do I need a CAD file to use the Vastu API?
No. Send rooms as coordinates, a DXF file, or an image of the plan for vastu-vision-detect to read.
How is the Vastu score calculated?
Each room is assessed against the rules for its type in the zones it occupies, weighted by floor area, with marma points, the entrance pada and the centre checked separately. The response explains its coverage and method.
Does it support the 16 zones and the 45 devatas?
Yes. The analysis uses the 16 directional zones and the 81-pada Vastu Purusha Mandala with its 45 devatas, and vastu-pada-grid returns the grid for drawing.
Can I compare two properties?
Yes. vastu-compare scores two plans, or one plan in two orientations, side by side.
Is the Vastu API suitable for a property portal?
Yes. It is designed for listings, buyer reports and filters, with honest coverage figures so the scores hold up when a buyer asks a consultant.
Get started
Try the ready-made plans from vastu-templates with a sandbox key, then read the Vastu API page for every capability. Sandbox calls are free, so you can design your Vastu screens before spending a credit.
Get the next guide by email
One email a month with new guides and API changes. No account needed.
Keep reading
- How to monetise an astrology app: models and cost scenarios
12 November 2026 · 9 min read
- Palm Reading API: how to add AI palmistry to your app
12 November 2026 · 9 min read
- Face Reading API: responsible AI face reading for apps
12 November 2026 · 7 min read



