Skip to main content
pūjāvāniby Chitram.AI

The Vaasthu engine, for your software

Pujavani reads a floor plan against classical and modern Vāstu rules and returns a scored reading together with the method that produced it. The same engine that runs the studio answers over an API, so a portal, a developer’s sales page or an architect’s tool can show a reading with its method beside it.

Try the sandboxRead the changelogRead a whole development

What the API does

Five families of routes. The generated contract, at /docs/openapi.json, lists every route; these are the ones an integration starts from.

Calculations

Session or API key

Read a plot, a room, a door or a whole plan against the rules. Each result carries the method it was read under.

  • POST/api/pujavani/vastu/auditMulti-room audit: centroid, Brahmasthan clearance, zone fit and a compliance score, with the method used.
  • POST/api/pujavani/vastu/ayadiThe six canonical Āyādi Ṣaḍvarga proportion tests for a plot.
  • POST/api/pujavani/vastu/ayadi/traditionsĀyādi for a plot under each named tradition, with the hasta used.
  • POST/api/pujavani/vastu/direction/bearingTrue-north bearing from a magnetic heading, corrected for the declination on the day it was read.
  • POST/api/pujavani/vastu/mandala/centroidShoelace centroid, area, aspect ratio and the Brahmasthan envelope.
  • POST/api/pujavani/vastu/mandala/16-zoneThe sixteen directional zones radiating from the centroid, each with the area it actually covers.
  • POST/api/pujavani/vastu/entrance/padaThe main door read against the thirty-two perimeter padas, by the tradition named.
  • POST/api/pujavani/vastu/room/evaluateOne room against the centroid and the central Brahmasthan clearance.
  • POST/api/pujavani/vastu/multi-storey/floor-rulesVertical prism collisions across floors.
  • POST/api/pujavani/vastu/specialized/evaluateA commercial or institutional layout against its sector's criteria.
  • POST/api/pujavani/vastu/optimizeRule-based layout suggestions; with a jurisdiction, a move its building codes forbid is withheld.
  • POST/api/pujavani/vastu/door-vedhaWhat stands in front of a door, read against the Bṛhat Saṃhitā's vedha verse.

Saved plans

Session or API key

Keep a plan for an organization, re-read it, share it read-only, and get its report. Saved plans are private to the organization that made them.

  • GET/api/pujavani/vastu/projectsThe organization's saved plans (is_template=false lists saved plans only).
  • POST/api/pujavani/vastu/projectsSave a floor plan; its score, entrance pada and Āyādi are computed from the drawing sent.
  • GET/api/pujavani/vastu/projects/{slug_or_id}One saved plan with its reading and method.
  • PUT/api/pujavani/vastu/projects/{slug_or_id}Edit a saved plan; a new drawing, plot size, north or options re-reads it.
  • POST/api/pujavani/vastu/projects/{slug_or_id}/recomputeRe-read a saved plan with the current engine.
  • POST/api/pujavani/vastu/projects/{slug_or_id}/shareMint, or keep, the plan's read-only share link.
  • GET/api/pujavani/vastu/projects/{slug_or_id}/reportThe plan's report, for the household or a committee, with the method, limits and signed readings.
  • GET/api/pujavani/vastu/projects/{slug_or_id}/practitioner-readingsThe practitioners' signed readings of a saved plan, withdrawn ones included.

Plan tools

Session or API key

Bring a drawing in, compare two readings, check a plan against building codes, and read a whole development.

  • POST/api/pujavani/vastu/plans/importRead a drawing (GeoJSON, SVG, ASCII DXF or IFC) into a canonical plan, with every assumption the importer made.
  • POST/api/pujavani/vastu/plans/overlayThe plan's zones, maṇḍala, Brahmasthan and door padas as a DXF or SVG overlay.
  • POST/api/pujavani/vastu/compareTwo plans read and set side by side; it never says which is better.
  • POST/api/pujavani/vastu/building-codes/checkThe plan's rooms against the building-code rules in force on a date, each finding with its clause.
  • POST/api/pujavani/vastu/building-codes/remedy-checkWhether moving a room's use or outline would breach a recorded building-code rule.
  • POST/api/pujavani/vastu/developer-auditsEvery unit type of a project read with one method, summarised with the date, the method and the disclaimer.

Reference

No key needed

The tables the readings are made against, and the benchmark plans an integration checks the engine with. Open to anyone; no key is needed.

  • GET/api/public/pujavani/vastu/reference/zonesThe sixteen directional zones of the modern practice.
  • GET/api/public/pujavani/vastu/reference/padasThe thirty-two entrance padas.
  • GET/api/public/pujavani/vastu/reference/devatasThe forty-five mandala devatas.
  • GET/api/public/pujavani/vastu/reference/room-matrixThe room by zone suitability score matrix.
  • GET/api/public/pujavani/vastu/reference/defectsThe classical dosha catalogue: code, severity, location, impact, remedy.
  • GET/api/public/pujavani/vastu/reference/building-codesThe recorded building-code jurisdictions, editions and rules, each with its clause and source.
  • GET/api/public/pujavani/vastu/reference/benchmarksThe public benchmark plans an integration can check the engine against.
  • GET/api/public/pujavani/vastu/reference/benchmarks/{benchmark_id}One benchmark plan with the output the engine is pinned to produce for it.
  • GET/api/public/pujavani/vastu/reference/changelogThe API's changelog, breaking changes marked.

Rite requests

Session or API key

Ask for an officiant-performed rite for an organization and read the desk's answer. No payment passes through: the fee is settled with the officiant.

  • POST/api/pujavani/rite-requestsAsk for a rite: when, where, and the saved plan it follows from. A person confirms.
  • GET/api/pujavani/rite-requestsThe organization's rite requests, newest first; status narrows to one state.
  • GET/api/pujavani/rite-requests/{request_id}One request, with the desk's answer when there is one.
  • POST/api/pujavani/rite-requests/{request_id}/cancelWithdraw a request that is still open.

Authenticate and meter

Authenticate

Every route answers to a signed-in session or to a tenant API key presented in the x-ojas-api-key header. An organization member with the right to manage API keys creates a key for themselves, limited to a role they choose; the key acts as that member and can only do less than they can. Its secret is shown once, when it is made.

Keys are created in the management console. Open API keys.

bash
curl "https://app.ojas.vc/api/pujavani/vastu/projects?is_template=false" \  -H "x-ojas-api-key: $OJAS_API_KEY"

Requests are throttled per key rather than per address. Every answer is a {"data": …} envelope, and a refusal says which of these it is:

  • 401No valid credential was presented.
  • 402The organization's plan does not include Vaasthu.
  • 403The credential's role lacks the privilege the route needs.
  • 404Not found, or not the organization's — another organization's row is never confirmed to exist.

Metering

Provisional

A calculation made with an API key counts against the plan’s api_calls allowance for the calendar month: 5,000 on the Vaasthu plan. Past it, the excess is reported as overage and the call still runs — nothing is refused for being over. A calculation made in the studio with a session is not counted.

The allowance is provisional, like the plan’s price, and may change before the plan is offered online.

Without a key

The reference tables, the benchmark plans and the changelog are open to anyone. Nothing needs to be made first.

bash
curl "https://app.ojas.vc/api/public/pujavani/vastu/reference/zones"

Try it without a key

Public benchmark plans, each with the output the engine is pinned to produce, so you can check an integration against a known answer. The reference tables are open too.

Read a whole development

Give each unit type of a project a name, a count and a plan, and read them all with one method. The summary is dated, weights the score bands by unit count, lists each unit type’s key doshas and carries the method and the disclaimer; it prints.

It needs an account, an organization, and the Vaasthu plan on it. Open the project audit.

Changelog

Showing a reading

A reading may be shown with its method block and this disclaimer beside it:

An advisory reading of classical and modern Vāstu rules against the plan you supplied. It is not structural, legal, planning, medical or financial advice, and it is not an approval or a certificate.

A reading is not relabelled certified, approved or guaranteed, and it is not used to exclude a buyer or a tenant on religion, caste or diet. When a reading is cited in advertising, the advertisement states the method, the tradition and the date it was made.

What is next

  • Data processing agreement Coming soon

    A standard agreement is drafted and needs legal review before it is offered.

  • Buying an API plan online Not built

    Today Pujavani’s team adds the Vaasthu plan to an organization on request. Paying for it by card, and published service levels, are not built.