Astrocartography API

planetary lines and relocation calculator

POST/astrology/astrocartographyPOST/astrology/relocation-chartPOST/astrology/local-space

Generate an astrocartography map of Midheaven, Imum Coeli, Ascendant, and Descendant planetary lines for any birth moment. Each line marks where a planet turns angular across the world, the core of relocation astrology and astro mapping. Returns right ascension, declination, the two meridian line longitudes, and sampled rising and setting curves ready to plot, with a short interpretation per line.

Location first, chart second

The Astrocartography 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 Astrocartography endpoint

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

Request

POST /api/v2/astrology/astrocartography

Parameters

ParameterTypeDescription
langquerystring enumResponse language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. Default en.
includequerystringOptional comma separated list of extra bodies to plot beyond the ten classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Unknown values are ignored. Defaults to none.

Request body

FieldTypeDescription
date*string (date)Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
time*string (time)Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
latitude*numberBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
longitude*numberBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
timezone*number or stringTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
nodeTypestring enumLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass "mean" to match those. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to "true".

Example request

POST /astrology/astrocartography
{
  "date": "1990-07-15",
  "time": "14:30:00",
  "latitude": 40.7128,
  "longitude": -74.006,
  "timezone": -5
}

Response

Structured JSON with documented fields, covered by 6,905 automated tests per deploy, 1,491 of them gold-standard tests verified against NASA JPL Horizons. Not hallucinated text.

200 OK
{
  "birthDetails": {
    "date": "1990-07-15",
    "time": "14:30:00",
    "latitude": 40.7128,
    "longitude": -74.006,
    "timezone": -5
  },
  "lines": [
    {
      "planet": "Sun",
      "rightAscension": 90.66,
      "declination": 23.44,
      "mc": {
        "longitude": -111.0142,
        "interpretation": "Your Sun Midheaven line runs through places where Self-awareness and ego comes forward in your public life, career, and reputation. Living or working along this line tends to push this part of you into the spotlight."
      },
      "ic": {
        "longitude": 68.9858,
        "interpretation": "Your Sun Imum Coeli line runs through places where Self-awareness and ego settles into your home, family, and inner foundations. This line deepens your sense of roots and private life."
      },
      "ascendant": {
        "points": [
          {
            "latitude": 40,
            "longitude": 139.7118
          }
        ],
        "circumpolarBeyond": 68.5262,
        "interpretation": "Your Sun Ascendant line runs through places where Self-awareness and ego colors your identity, vitality, and how you first come across to others. This part of you feels switched on here."
      },
      "descendant": {
        "points": [
          {
            "latitude": 40,
            "longitude": -1.7402
          }
        ],
        "circumpolarBeyond": 68.5262,
        "interpretation": "Your Sun Descendant line runs through places where Self-awareness and ego shapes your close relationships, partnerships, and the people you attract. Connection themes stand out along this line."
      }
    }
  ],
  "summary": "Astrocartography lines for 1990-07-15. 10 bodies, each with Midheaven, Imum Coeli, Ascendant, and Descendant lines mapping where their themes turn angular worldwide for relocation planning."
}

Response fields

FieldTypeDescription
birthDetails*objectEcho of the birth moment and place used to compute every planetary line.
birthDetails.date*string (date)Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
birthDetails.time*string (time)Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
birthDetails.latitude*numberBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
birthDetails.longitude*numberBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
birthDetails.timezone*numberTimezone offset from UTC in decimal hours. Examples: New York = -5, London = 0, India = 5.5, Tokyo = 9.
lines*array of objectOne entry per body, each carrying its Midheaven, Imum Coeli, Ascendant, and Descendant planetary lines for relocation mapping.
lines[].planet*stringCelestial body this set of planetary lines belongs to. Always English, whatever the lang parameter says, so it stays safe to compare against in code. Use planetLocalized for anything a reader sees.
lines[].planetLocalizedstringBody name in the requested language, for display only. Present only when lang is set to a language other than English, since in English it would repeat its canonical partner field exactly. Never compare against this value, compare against the canonical field beside it.
lines[].symbolstringUnicode astronomical symbol for this body.
lines[].rightAscension*numberEquatorial right ascension of the body in degrees (0 to 360), the basis for every line.
lines[].declination*numberEquatorial declination of the body in degrees (-90 to 90), which sets how far the rising and setting lines curve.
lines[].mc*objectMidheaven (MC) line. Places along this meridian where the body was culminating overhead, tied to public life, career, and reputation.
lines[].mc.longitude*numberConstant geographic longitude of this vertical meridian line in decimal degrees. The body culminates (MC) along it, so plot it as a straight north to south line.
Show all fields
FieldTypeDescription
lines[].mc.interpretation*stringPlain language meaning of this Midheaven planetary line for relocation, suitable for chart reports and AI agents.
lines[].ic*objectImum Coeli (IC) line, opposite the MC. Places where the body was anti-culminating, tied to home, family, and inner foundations.
lines[].ic.longitude*numberConstant geographic longitude of this vertical meridian line in decimal degrees. The body anti-culminates (IC) along it, so plot it as a straight north to south line.
lines[].ic.interpretation*stringPlain language meaning of this Imum Coeli planetary line for relocation, suitable for chart reports and AI agents.
lines[].ascendant*objectAscendant (rising) line. Places where the body was on the eastern horizon, tied to identity, vitality, and self-expression.
lines[].ascendant.points*array of objectSampled geographic points tracing this rising line from 70 South to 70 North. Join them in latitude order to draw the curved planetary line on a world map.
lines[].ascendant.points[].latitude*numberGeographic latitude of this sampled point in decimal degrees.
lines[].ascendant.points[].longitude*numberGeographic longitude in decimal degrees where the body sits exactly on the eastern (rising) horizon at this latitude.
lines[].ascendant.circumpolarBeyond*numbernullAbsolute latitude in degrees beyond which the body never crosses the horizon, so the line has no points past it. Null when the line spans the full sampled range.
lines[].ascendant.interpretation*stringPlain language meaning of this rising (Ascendant) planetary line for relocation, suitable for chart reports and AI agents.
lines[].descendant*objectDescendant (setting) line. Places where the body was on the western horizon, tied to relationships and partnerships.
lines[].descendant.points*array of objectSampled geographic points tracing this setting line from 70 South to 70 North. Join them in latitude order to draw the curved planetary line on a world map.
lines[].descendant.points[].latitude*numberGeographic latitude of this sampled point in decimal degrees.
lines[].descendant.points[].longitude*numberGeographic longitude in decimal degrees where the body sits exactly on the western (setting) horizon at this latitude.
lines[].descendant.circumpolarBeyond*numbernullAbsolute latitude in degrees beyond which the body never crosses the horizon, so the line has no points past it. Null when the line spans the full sampled range.
lines[].descendant.interpretation*stringPlain language meaning of this setting (Descendant) planetary line for relocation, suitable for chart reports and AI agents.
summary*stringShort overview of the astrocartography map for previews and report intros.

Supported options

lang

entrdeeshiptfrru

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.astrology.generateAstrocartography({ body: { date: '1990-07-15', time: '14:30:00', latitude: 40.7128, longitude: -74.006, timezone: -5 } })
Install: npm install @roxyapi/sdk

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

More Astrocartography endpoints

The Astrocartography API bundles these related endpoints under one key.

POST/astrology/relocation-chart

Generate relocation chart - Relocated birth chart calculator with shifted houses and angles

Calculate a relocation chart (relocated birth chart) for a new place on Earth. The birth moment stays the same, so every planet keeps its natal sign and degree, while the Ascendant, Midheaven, Vertex, and all twelve house cusps are recomputed for the new latitude and longitude. Returns the relocated houses and angles, the planets that change house, the angular planets activated at the new place, and the distance and compass direction from the birthplace. Built for relocation astrology readings, astrocartography style move planning, and travel charts. Verified against NASA JPL Horizons.

Try it live
POST/astrology/local-space

Local space astrology map - Directional planetary compass lines

Generate a local space astrology map that projects the natal planets onto the local horizon as compass directions and great-circle lines radiating from the birthplace. Returns each body azimuth (degrees clockwise from true north), altitude, 16-point compass direction, whether it sits above the horizon, and the latitude and longitude waypoints of its directional line. Ideal for relocation planning, directional astrology, and travel-direction maps.

Try it live

Remote MCP for AI agents

Every Western 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-astrology https://roxyapi.com/mcp/astrology \
  --header "X-API-Key: YOUR_KEY"

Tool name for POST /astrology/astrocartography: post_astrology_astrocartography. Full MCP setup guide

What you can build

Launch natal chart apps with professional-grade accuracy: birth charts, planet positions, house placements, aspects, and element analysis ready for your UI in days

Add zodiac compatibility scoring to dating apps: synastry analysis, composite charts, and compatibility scores with detailed relationship dynamics

Ship personalized horoscope platforms: publisher-grade daily, weekly, and monthly forecasts with unique content per sign, active transit metadata, Moon phase data, and date scheduling for editorial pre-publishing

Build AI astrology chatbots with MCP: your OpenAI, Claude, or Gemini agent auto-discovers and calls every astrology endpoint with zero integration code

Power wellness and lifestyle apps with real-time transits, moon phase calendars, solar returns, and planetary movement alerts for self-discovery features

Create astrology content engines: automated zodiac content with house-based uniqueness per sign, horoscope newsletters with real lunar event dates, transit alerts, and seasonal forecasts at scale

Drop-in UI components & widgets

Render Astrocartography API responses without building charts yourself. Install the npm package and drop these into Next.js, React, Vue, Svelte, Angular, or plain HTML, or embed the very same component on Squarespace, Wix, or WordPress by pasting one snippet, with no backend and no build step. They belong to one library that covers the entire spiritual stack rather than astrology alone, MIT licensed and included in every plan at no extra cost, never a separate product and never an upsell. The Astrocartography API calculations, the interface that renders them, and the Remote MCP your agent calls, all behind one key, end to end.

MIT licensedFramework agnosticThemeable via CSS variablesnpm or CDN
Show all Astrocartography UI components
ElementRenders
<roxy-astrocartography-map>World map of planetary MC, IC, Ascendant, and Descendant lines with per-line interpretations
<roxy-local-space-compass>Compass dial of planetary azimuth lines from the birthplace, dimmed below the horizon
<roxy-relocation-wheel>Relocated chart wheel plus the move geometry, angular planets, and planets that change house

Related capabilities

Astrocartography API FAQ

What does the Astrocartography API return?

Generate an astrocartography map of Midheaven, Imum Coeli, Ascendant, and Descendant planetary lines for any birth moment. 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 Astrocartography 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 Astrocartography 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 Astrocartography 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 Astrocartography 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/astrology over Streamable HTTP, so Claude, ChatGPT, Cursor, and any MCP client auto-discover it with no local setup or Docker.

How is the Astrocartography 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 Astrocartography API is included at no extra cost.

What lang values does the Astrocartography API accept?

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

Start using Astrocartography API today.

Ship your astrology app this weekend. Not this quarter.

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