Gemstone (ratna) report PDF

The astrology is the JSON endpoint verbatim, and a test compares the two across the whole zodiac for both schools so they cannot drift: same sidereal lagna, same rules, same three gems. What the document adds is what a table cannot carry. Each gem gets the traditional significations of its graha rather than a claim about the stone, and each gets a first-wearing date found by scanning the Panchang for the nearest favourable day that falls on that graha's own weekday. When no auspicious day lands on that weekday inside the window the report says so instead of printing a date that ignored it, because on paper the two look identical.

curl -X POST https://api.astroway.info/v1/reports/gemstone \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
  "chart": {
    "date": "1990-05-15",
    "time": "14:30:00",
    "timezoneOffset": 3,
    "latitude": 50.45,
    "longitude": 30.52
  },
  "school": "lagna-lord",
  "wearingFrom": "2026-09-01",
  "language": "en"
}'

{
  "ok": true,
  "data": {
    "url": "https://api.astroway.info/reports/abc-gemstone.pdf",
    "storage_key": "reports/abc-gemstone.pdf",
    "byte_length": 135145,
    "page_count": 7,
    "duration_ms": 1537,
    "expires_at": "2026-08-14T06:33:00.000Z"
  }
}

Use it as the paid tier over the JSON: an app can render the prescription itself, and this is the artefact a customer pays for and keeps. It is also the honest form for a remedy, because a document has room for the boundary that a JSON field does not: gem identity, treatment and weight belong to a gemmologist, and no stone substitutes for medical care.

The school is named on the cover on purpose. The two schools prescribe the same gems and withhold different ones, so a document that hid which produced it would be less honest than the data it was built from. Under the lagna-lord school the ownership table drops the functional-role column entirely rather than importing the other school's verdict, which would read as "do not wear a diamond" in a report that never said so. Coordinates are required: a prescription cast at 0N 0E is a confident document about the wrong ascendant, and unlike a JSON field a PDF outlives the request.