Quick Start Playground SDK MCP Setup Free Templates AGENTS.md

KP Astrology API

Generate complete KP birth chart

POST/vedic-astrology/kp/chartGET/vedic-astrology/kp/ayanamsaPOST/vedic-astrology/kp/cuspsPOST/vedic-astrology/kp/planetsPOST/vedic-astrology/kp/planets-intervalPOST/vedic-astrology/kp/rasi-changesPOST/vedic-astrology/kp/ruling-planetsPOST/vedic-astrology/kp/ruling-planets-intervalPOST/vedic-astrology/kp/sublord-changes

Get API Key Try it live

Remote MCP server OpenAPI schema

Rated 4.5 by 127 developers

Includedwith every plan(at no extra cost)

Astrology Numerology Tarot Human Design Forecast Biorhythm I-Ching Crystals Dreams Angel Numbers Location

828 gold-standard tests, NASA JPL verified

12 domains, 1 API key

llms.txt for AI agents

Generate authentic Krishnamurti Paddhati birth charts with Placidus house cusps, star-lord and sub-lord calculations. Supports custom ayanamsa and dynamic KP-Newcomb ayanamsa calculation. Returns complete chart with all 9 planets (Sun through Ketu), Ascendant, 12 Placidus house cusps, nakshatra details, star-lords, sub-lords, and KP horary numbers (1-249). Perfect for KP astrology software, horary prediction apps, and event timing analysis. SEO: KP astrology chart API, Placidus house cusps planets, Krishnamurti Paddhati chart generator, KP birth chart calculator

Location first, chart second

The KP Astrology API needs latitude, longitude, and timezone. Never ask users to type coordinates. Resolve a city with the Location endpoint first, then feed the result into the request. Timezone accepts a decimal offset or an IANA name.

1 Resolve the location

GET

curl "https://roxyapi.com/api/v2/location/search?q=New York" \
  -H "X-API-Key: YOUR_KEY"
# -> cities[0]: { latitude, longitude, timezone: "America/New_York" }

2 Call the KP Astrology endpoint

POST /vedic-astrology/kp/chart

# feed latitude, longitude and timezone from step 1
POST https://roxyapi.com/api/v2/vedic-astrology/kp/chart

Request

POST /api/v2/vedic-astrology/kp/chart

Parameters

Parameter	Type	Description
langquery	string enum	Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. Default `en`.

Request body

Field	Type	Description
date*	string (date)	Birth date in YYYY-MM-DD format
time*	string (time)	Birth time in 24-hour HH:MM:SS format. CRITICAL for accurate Lagna and house calculations.
latitude*	number	Birth location latitude in decimal degrees
longitude*	number	Birth location longitude in decimal degrees
timezone	number or string	Timezone offset from UTC in hours. Defaults to 5.5 (IST) for Vedic astrology.
ayanamsa	string enum	Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
ayanamsaValue	number	Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
nodeType	string enum	Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1.5 degrees from mean with a 173-day period. Impacts KP sub-lord assignments in narrow boundary cases. Defaults to "mean".

Example request

POST /vedic-astrology/kp/chart

{
  "date": "1990-07-04",
  "time": "10:12:00",
  "latitude": 28.6139,
  "longitude": 77.209
}

Response

Structured JSON with documented fields, verified against NASA JPL Horizons across 828 gold-standard tests. Not hallucinated text.

200 OK

{
  "meta": {
    "date": "1990-07-04",
    "time": "10:12:00",
    "latitude": 28.6139,
    "longitude": 77.209,
    "timezone": 5.5,
    "ayanamsa": 0,
    "ayanamsaType": "string",
    "houseSystem": "string"
  },
  "ascendant": {
    "longitude": 0,
    "sign": "string",
    "signLord": "Venus",
    "nakshatra": "string",
    "nakshatraLord": "string",
    "pada": 0,
    "starLord": "string",
    "subLord": "string",
    "subSubLord": "string",
    "kpNumber": 0
  },
  "cusps": [
    {
      "house": 0,
      "longitude": 0,
      "sign": "string",
      "signLord": "string",
      "nakshatra": "string",
      "nakshatraLord": "string",
      "pada": 0,
      "starLord": "string",
      "subLord": "string",
      "subSubLord": "string",
      "kpNumber": 0
    }
  ],
  "planets": [
    {
      "planet": "string",
      "longitude": 0,
      "sign": "string",
      "house": 0,
      "nakshatra": "string",
      "nakshatraLord": "string",
      "pada": 0,
      "starLord": "string",
      "subLord": "string",
      "subSubLord": "string",
      "kpNumber": 0,
      "retrograde": true
    }
  ],
  "nodes": {
    "rahu": {
      "longitude": 0,
      "sign": "string",
      "house": 0,
      "nakshatra": "string",
      "starLord": "string",
      "subLord": "string",
      "subSubLord": "string",
      "kpNumber": 194
    },
    "ketu": {
      "longitude": 0,
      "sign": "string",
      "house": 0,
      "nakshatra": "string",
      "starLord": "string",
      "subLord": "string",
      "subSubLord": "string",
      "kpNumber": 194
    }
  },
  "significators": {
    "houseWise": [
      {
        "house": 7,
        "significators": [
          {
            "level": 1,
            "description": "Planets in star of occupant",
            "planets": [
              "Venus",
              "Mars"
            ]
          }
        ],
        "all": [
          "Venus",
          "Mars",
          "Jupiter"
        ]
      }
    ],
    "planetWise": [
      {
        "planet": "Venus",
        "signifies": [
          {
            "level": 1,
            "houses": [
              7,
              2
            ]
          }
        ],
        "allHouses": [
          7,
          2,
          11
        ]
      }
    ]
  }
}

Response fields

Field	Type	Description
meta*	object	Chart metadata including birth data, ayanamsa, and house system.
meta.date*	string	Birth date in YYYY-MM-DD format used for this KP chart calculation.
meta.time*	string	Birth time in HH:MM:SS format used for Lagna and Placidus cusp calculations.
meta.latitude*	number	Birth location latitude in decimal degrees. Determines Placidus house cusps and Ascendant.
meta.longitude*	number	Birth location longitude in decimal degrees. Affects local sidereal time for house calculations.
meta.timezone*	number	Timezone offset from UTC in decimal hours used for time conversion.
meta.ayanamsa*	number	KP Newcomb ayanamsa value in degrees. Precession correction applied to convert tropical to sidereal positions.
meta.ayanamsaType*	string	Ayanamsa system used (KP Newcomb).
meta.houseSystem*	string	House system used (Placidus, standard for KP astrology).
ascendant*	object	Ascendant (Lagna) details with full KP stellar hierarchy.
ascendant.longitude*	number	Sidereal longitude of Ascendant (Lagna) in degrees.
ascendant.sign*	string	Zodiac sign of the Ascendant.
ascendant.signLord*	string	Ruling planet of the Ascendant sign (the rashi lord). In KP this is the weakest of the four lords, ranked below the star lord and sub lord, but it still sets the broad temperament of the Lagna.
ascendant.nakshatra*	string	Nakshatra (star) of the Ascendant.

Show all fields

Field	Type	Description
ascendant.nakshatraLord*	string	Lord of the Ascendant nakshatra.
ascendant.pada*	number	Nakshatra pada (1-4) of the Ascendant.
ascendant.starLord*	string	KP star lord of the Ascendant position.
ascendant.subLord*	string	KP sub lord of the Ascendant. crucial for KP predictions. The Ascendant sub lord determines overall life promise.
ascendant.subSubLord*	string	KP sub-sub lord (SSL) of the Ascendant. Third level of the Vimshottari subdivision hierarchy, used for fine-tuning predictions.
ascendant.kpNumber*	number	KP number (1-249) for the Ascendant degree.
cusps*	array of object	All 12 Placidus house cusps with KP stellar hierarchy. Cusp sub lords are the primary predictive tool in KP astrology.
cusps[].house*	number	House number (1-12).
cusps[].longitude*	number	Placidus cusp longitude in sidereal degrees.
cusps[].sign*	string	Zodiac sign at the cusp.
cusps[].signLord*	string	Lord of the zodiac sign at the cusp (house owner).
cusps[].nakshatra*	string	Nakshatra at the cusp degree.
cusps[].nakshatraLord*	string	Lord of the nakshatra at the cusp.
cusps[].pada*	number	Nakshatra pada (1-4) at the cusp.
cusps[].starLord*	string	KP star lord of the cusp.
cusps[].subLord*	string	KP sub lord of the cusp. the deciding factor for house-level predictions in KP astrology.
cusps[].subSubLord*	string	KP sub-sub lord (SSL) of the cusp. Third level of Vimshottari subdivision for fine-grained cusp analysis.
cusps[].kpNumber*	number	KP number (1-249) for the cusp degree.
planets*	array of object	Positions of all 7 visible planets with complete KP stellar breakdown.
planets[].planet*	string	Planet name (Sun through Saturn, 7 visible planets).
planets[].longitude*	number	Sidereal longitude in degrees (KP ayanamsa corrected).
planets[].sign*	string	Zodiac sign the planet occupies.
planets[].house*	number	House number (1-12) based on Placidus cusps.
planets[].nakshatra*	string	Nakshatra the planet occupies.
planets[].nakshatraLord*	string	Nakshatra lord (same as star lord).
planets[].pada*	number	Nakshatra pada (1-4).
planets[].starLord*	string	KP star lord, determines primary house signification.
planets[].subLord*	string	KP sub lord, the decisive factor. Planet gives results of the houses signified by its sub lord.
planets[].subSubLord*	string	KP sub-sub lord (SSL) of the planet. Third level of Vimshottari subdivision for precise timing analysis.
planets[].kpNumber*	number	KP number (1-249).
planets[].retrograde*	boolean	True if planet is retrograde. Retrograde planets may delay or deny results in KP system.
nodes*	object	Lunar nodes (Rahu and Ketu) with KP stellar hierarchy. Nodes are powerful agents that amplify the significations of their dispositors.
nodes.rahu*	object	Rahu (North Lunar Node), shadow planet, always retrograde, acts as agent of its sign lord and star lord.
nodes.rahu.longitude*	number	Sidereal longitude of Rahu (North Node).
nodes.rahu.sign*	string	Zodiac sign Rahu occupies.
nodes.rahu.house*	number	Occupied house number (1-12) based on Placidus cusps.
nodes.rahu.nakshatra*	string	Nakshatra of Rahu.
nodes.rahu.starLord*	string	KP star lord of Rahu.
nodes.rahu.subLord*	string	KP sub lord of Rahu.
nodes.rahu.subSubLord*	string	KP sub-sub lord (SSL) of Rahu.
nodes.rahu.kpNumber*	number	KP number (1-249) locating Rahu in the 249-division sub-lord scheme. Each of the 249 divisions maps to a unique sign, star lord and sub lord triple, so one integer pins the position precisely enough for KP event timing.
nodes.ketu*	object	Ketu (South Lunar Node), shadow planet, spiritual karmic indicator.
nodes.ketu.longitude*	number	Sidereal longitude of Ketu (South Node). Always 180 degrees from Rahu.
nodes.ketu.sign*	string	Zodiac sign Ketu occupies.
nodes.ketu.house*	number	Occupied house number (1-12) based on Placidus cusps.
nodes.ketu.nakshatra*	string	Nakshatra of Ketu.
nodes.ketu.starLord*	string	KP star lord of Ketu.
nodes.ketu.subLord*	string	KP sub lord of Ketu.
nodes.ketu.subSubLord*	string	KP sub-sub lord (SSL) of Ketu.
nodes.ketu.kpNumber*	number	KP number (1-249) locating Ketu in the 249-division sub-lord scheme. Each of the 249 divisions maps to a unique sign, star lord and sub lord triple, so one integer pins the position precisely enough for KP event timing.
significators*	object	KP significators for event prediction and timing. Shows which planets signify each house (house-wise) and which houses each planet signifies (planet-wise). Strength order: Level 1 (planets in star of occupant) > Level 2 (occupants) > Level 3 (planets in star of owner) > Level 4 (house owner).
significators.houseWise*	array of object
significators.houseWise[].house*	number	House number 1-12
significators.houseWise[].significators*	array of object
significators.houseWise[].significators[].level*	number	KP significator strength level (1-4). L1: planets in star of occupant (strongest). L2: occupant itself. L3: planets in star of owner. L4: sign owner. Lower number = stronger signification for this house.
significators.houseWise[].significators[].description*	string	Human-readable label for this KP significator level.
significators.houseWise[].significators[].planets*	array of string	Planets signifying this house at this strength level.
significators.houseWise[].all*	array of string	All significators in order of strength
significators.planetWise*	array of object
significators.planetWise[].planet*	string	Vedic graha (planet) being analyzed for its house significations.
significators.planetWise[].signifies*	array of object
significators.planetWise[].signifies[].level*	number	KP significator strength level (1-4). L1 strongest, L4 weakest.
significators.planetWise[].signifies[].houses*	array of number	House numbers this planet signifies at this strength level.
significators.planetWise[].allHouses*	array of number	All houses signified in order of strength

Supported options

lang

entrdeeshiptfrru

ayanamsa

kp-newcombkp-oldlahiricustom

nodeType

meantrue

Call it in your language in seconds.

Every snippet is generated from the live OpenAPI spec, so method names, parameters, and fields always match production.

TypeScript

import { createRoxy } from '@roxyapi/sdk'

const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.vedicAstrology.generateKpChart({ body: { date: '1990-07-04', time: '10:12:00', latitude: 28.6139, longitude: 77.209 } })

Install: npm install @roxyapi/sdk

Python

from roxy_sdk import create_roxy

roxy = create_roxy("YOUR_API_KEY")
result = roxy.vedic_astrology.generate_kp_chart(date='1990-07-04', time='10:12:00', latitude=28.6139, longitude=77.209)

Install: pip install roxy-sdk

PHP

use function RoxyAPI\Sdk\createRoxy;

$roxy = createRoxy(getenv('ROXY_API_KEY'));
$result = $roxy->vedicAstrology->generateKpChart(date: '1990-07-04', time: '10:12:00', latitude: 28.6139, longitude: 77.209);

Install: composer require roxyapi/sdk

using RoxyApi;

var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
var result = await roxy.VedicAstrology.Kp.Chart.PostAsync(new() { /* request fields above */ });

Install: dotnet add package RoxyApi.Sdk

import roxyapi "github.com/RoxyAPI/sdk-go"

roxy, _ := roxyapi.NewRoxy(os.Getenv("ROXY_API_KEY"))
resp, _ := roxy.VedicAstrology.GenerateKpChart(ctx, nil, roxyapi.GenerateKpChartJSONRequestBody{ /* request fields above */ })

Install: go get github.com/RoxyAPI/sdk-go

cURL

curl -X POST "https://roxyapi.com/api/v2/vedic-astrology/kp/chart" \
  -H "X-API-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"1990-07-04","time":"10:12:00","latitude":28.6139,"longitude":77.209}'

Prefer to try before you write code? Run this Vedic Astrology endpoint live in the API playground and inspect a real production response.

More KP Astrology endpoints

The KP Astrology API bundles these related endpoints under one key.

GET/vedic-astrology/kp/ayanamsa

Get KP-Newcomb ayanamsa - Dynamic daily calculation

Get real-time KP-Newcomb ayanamsa value calculated using Newcomb precession theory - no preset tables. Returns precise ayanamsa for any date based on IAU modern precession standards. Essential for accurate KP chart calculations and research. Formula: A = 16.90709×(Year/10000) - 0.757371×(Year/1000)² - 6.92416, B = (Month-1 + Date/30)×1.1574074/1000. KP Newcomb ayanamsa API, dynamic ayanamsa calculator, Krishnamurti ayanamsa today, current KP ayanamsa

Try it live

POST/vedic-astrology/kp/cusps

Get KP Placidus house cusps with sub-lords

Calculate unequal Placidus house cusps with ruling sign-lord, nakshatra-lord, and sub-lord for each cusp. Dynamic KP-Newcomb or custom ayanamsa support. Used in KP horary astrology, cusp sub-lord analysis, and birth chart rectification. Returns all 12 house cusps with KP sub-division details. SEO: Placidus house cusps API, KP cusp calculator, house cusps star sub lord, KP horary cusps

Try it live

POST/vedic-astrology/kp/planets

Get KP planetary positions with sub-lords

Get planetary positions with detailed KP star-lord and sub-lord calculations for precise event timing and significator analysis. Returns all 9 planets (Sun through Ketu) with nakshatra, star-lord, sub-lord, and KP horary numbers (1-249). Essential for KP astrology software, significator analysis, and event prediction. KP planet positions API, star lord sub lord calculator, KP significator API, Krishnamurti Paddhati planets

Try it live

POST/vedic-astrology/kp/planets-interval

Get KP planets at time intervals

Calculate positions of all 9 planets (Sun through Saturn, Rahu, Ketu) at regular time intervals with full KP hierarchy: sign lord, star lord, sublord, and sub-sublord. Returns longitude, zodiac sign, nakshatra, sublord, sub-sublord, and KP number (1-249) for each planet at each timestamp. Ideal for tracking planetary motion, finding optimal muhurta windows, analyzing transit patterns, and building KP ephemeris tables. Maximum range of 7 days with 15-minute to 24-hour intervals.

Try it live

POST/vedic-astrology/kp/rasi-changes

Find KP rasi ingress times

Track when planets enter new zodiac signs (rasi) with precise ingress timestamps. Essential for Vedic astrology transit analysis, muhurta selection, and predictive horoscope readings. Returns exact times when planets cross sign boundaries (0, 30, 60 degrees etc). Use for tracking Sun sankranti dates, Moon sign changes for panchang, or outer planet transits for yearly predictions.

Try it live

POST/vedic-astrology/kp/ruling-planets

Get KP ruling planets with optional significators

Calculate the 5 ruling planets at any moment using Krishnamurti Paddhati horary astrology. Returns Day Lord, Moon Sign/Star/Sub Lord, Lagna Sign/Star/Sub Lord. Optionally provide birth data (birthDate, birthTime) to include significators showing which houses each ruling planet signifies in the birth chart - essential for KP prediction.

Try it live

POST/vedic-astrology/kp/ruling-planets-interval

Get KP ruling planets with significators at intervals

Calculate ruling planets and their KP significators at regular time intervals using Krishnamurti Paddhati prashna (horary) astrology. For each interval, a full Placidus house chart is erected and significators are computed using the 4-level KP hierarchy: Level 1 (strongest) planets in star of house occupant, Level 2 occupants, Level 3 planets in star of house owner, Level 4 house owner. Returns Day Lord (sunrise-based Hindu Vara), Moon Sign/Star/Sub/Sub-Sub Lords, Lagna Sign/Star/Sub/Sub-Sub Lords, unique ruling planets set, and per-ruling-planet house significations. No birth data needed, significators come from each moments sky chart. Use for birth time rectification, muhurta selection, and KP horary number analysis.

Try it live

POST/vedic-astrology/kp/sublord-changes

Find KP sublord changes

Track when planets cross KP sublord boundaries (1-249 divisions) for precise Krishnamurti Paddhati event timing. Returns exact timestamps when a planet transitions between sublords, essential for prashna kundali analysis and dasha predictions. Use this to find favorable windows when benefic sublords are active. Supports Sun, Moon, Mars, Mercury, Jupiter, Venus, and Saturn tracking over any date range.

Try it live

Remote MCP for AI agents

Every Vedic Astrology endpoint is a callable tool on the Remote MCP server over Streamable HTTP. No local setup, no Docker. Claude, ChatGPT, Cursor, and any MCP client auto-discover the tools and ground their answers in verified data.

Claude Code / Cursor

claude mcp add --transport http \
  roxy-vedic-astrology https://roxyapi.com/mcp/vedic-astrology \
  --header "X-API-Key: YOUR_KEY"

Tool name for POST /vedic-astrology/kp/chart: post_vedic_astrology_kp_chart. Full MCP setup guide

What you can build

Matrimonial matchmaking platforms - automate Gun Milan compatibility scoring, Manglik dosha checks, Navamsa spouse analysis, and generate match reports with remedies for Shaadi.com-style features

Daily horoscope and prediction apps - fetch planetary transits, current Dasha periods, Panchang data, and birth star forecasts to power personalized daily readings at consumer-app scale

Kundli generation and PDF report services - combine D1/D9 charts, planetary positions, Dasha timelines, yoga detection, and dosha analysis into automated birth chart reports

KP horary and event prediction apps - build stellar astrology software with significator analysis, cusp sub-lords, and 249-level precision for answering when/yes-no questions

Spiritual wellness and calendar apps - integrate Panchang for Hindu festival dates, fasting calendars, temple muhurat selection, and Nakshatra-based meditation schedules

AI astrology chatbots and virtual consultants - power conversational AI with structured Vedic calculations, compatibility queries, Dasha predictions, and remedy suggestions via ChatGPT plugins or MCP integration

Drop-in UI components

Render KP Astrology API responses without building charts yourself. These open source, framework-agnostic web components take the typed response and draw it, in React, Vue, Svelte, Angular, plain HTML, and WordPress.

<roxy-kp-chart><roxy-kp-planets-table><roxy-kp-ruling-planets>

See them live on Roxy UI

Related capabilities

Kundli API

Panchang API

Vimshottari Dasha API

Nakshatra API

Manglik Dosha API

All of Vedic Astrology API

KP Astrology API FAQ

What does the KP Astrology API return?

Generate authentic Krishnamurti Paddhati birth charts with Placidus house cusps, star-lord and sub-lord calculations. Every response is structured JSON with documented fields, not free text, so you map it straight into your product.

How do I authenticate with the KP Astrology API?

Pass your key in the X-API-Key header on every request. Keys are delivered instantly at checkout with no approval queue. Use a secret sk key server side, or mint a publishable pk key locked to your origins for browser and no-code use.

Does the KP Astrology API support multiple languages?

Yes. Append the lang query parameter to any endpoint for responses in English, German, Spanish, French, Hindi, Portuguese, Russian and Turkish. The translated payload includes the full interpretation text, not just field labels.

Do I need coordinates to call the KP Astrology API?

No. Call GET /location/search with a city name first, then pass latitude, longitude, and timezone from the first result into the request. Never ask users to type coordinates. Timezone accepts a decimal offset or an IANA name.

Is the KP Astrology API available over Remote MCP for AI agents?

Yes. Every endpoint is exposed as a callable tool on the Remote MCP server at https://roxyapi.com/mcp/vedic-astrology over Streamable HTTP, so Claude, ChatGPT, Cursor, and any MCP client auto-discover it with no local setup or Docker.

How is the KP Astrology API billed?

Flat pricing: 1 request equals 1 quota unit, REST and MCP identical, with no credit weighting or per-token markup. Every plan includes all 12 domains, so the KP Astrology API is included at no extra cost.

What lang values does the KP Astrology API accept?

The lang parameter accepts en, tr, de, es, hi, pt, fr, ru. Case-insensitive where it is a path value.

Start using KP Astrology API today.

Launch your Jyotish or KP astrology product in days. Not months.

All 12 domains included with every plan. Every endpoint, MCP server, SDK, and starters.

Plans from $39/mo, starting at $2.70 per domain on annual billing. No credit card required for testing.

View Pricing & Get API Key