POST/v1/nadi/lens

Nadi · Lens API

Bhrigu/Nadi lens - chara-karakas, graha significations, conjunctions, Nadiamsa signature.

About the engine

Part of the Nadi engine

Nadi astrology reads the chart at its finest grain. The Nadiamsa (D150) divides every sign into 150 parts of 0°12′ - the deepest classical subdivision - and four lenses read it: the Bhrigu lens (each graha as a karaka, with the soul + spouse significators), the Dhruva meaning layer (each body's archetype, modified by sign, lord and dignity, resolved into soul blueprint, gifts, karma, wealth and evolution), and the Chandra Kala timing layer (sequence, manifestation and birth-time rectification). Meaning + timing, from the most birth-time-sensitive layer in the whole engine.

Request

Try it from the command line

curl -X POST 'https://api.astronode.dev/v1/nadi/lens' \
  -H 'Authorization: Bearer aie_test_REPLACE_WITH_YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  --data '{
  "date": "1993-07-04",
  "time": "09:27:11",
  "tz_offset_minutes": 330,
  "lat": 31.7473,
  "lng": 77.7754
}'

Paste and run - this is the exact payload our live playground sends to this endpoint, so it is valid against the current schema. Every AstroNode endpoint needs a bearer token from your dashboard. Test keys (aie_test_*) work on the free tier - 1,000 requests / month, no card.

Request schema

Fields POST /v1/nadi/lens accepts

Request body fields for POST /v1/nadi/lens
FieldTypeNotes
daterequiredstring

pattern ^\d{4}-\d{2}-\d{2}$

e.g. 1993-07-04

timerequiredstring

pattern ^\d{2}:\d{2}(:\d{2})?$

e.g. 09:27:11

tz_offset_minutesrequiredinteger

Offset from UTC in minutes (e.g., 330 for IST)

-840..840

e.g. 330

latrequirednumber

-90..90

e.g. 31.7473

lngrequirednumber

-180..180

e.g. 77.7754

Generated from the same OpenAPI 3.1 document the API validates against, so this table cannot drift from the endpoint without the build failing.

Response

What you get back

Every AstroNode response uses the same envelope: request_id, data (the endpoint-specific payload), interpretation (optional narrative block), and meta (engine version + computed_at timestamp). This endpoint documents 200, 400, 401, 429.

The data payload for POST /v1/nadi/lens is not yet broken out field by field in the published schema. The fastest way to see its exact shape is to run the call - the playground returns a live response with no signup, and the API reference carries the full document.

Engine highlights

What the Nadi engine ships

  • Nadiamsa (D150) - the finest subdivision, 150 per sign (1800 across the zodiac)
  • Chara-karakas: Atmakaraka (soul) + Darakaraka (spouse) significators
  • Dhruva meaning layer - soul blueprint, hidden gifts/challenges, relationship, karma, wealth, evolution
  • Chandra Kala timing layer - timing, manifestation, validation, event correlation, rectification
  • Bhrigu lens - each graha as a karaka; conjunctions read as blended themes

Ready to call POST /v1/nadi/lens?

Free tier covers 1,000 requests / month. Razorpay-billed, GST-compliant invoices when you upgrade.

Informational, not predictive. Not medical, legal, or financial advice.