---
title: "Calculate Astrocartography Power Lines"
method: POST
path: "/acg/power-lines"
tags: ["ACG"]
---

# Calculate Astrocartography Power Lines

`POST /acg/power-lines`

## Request

- Base URL: `https://api.openephemeris.com`
- URL: `https://api.openephemeris.com/acg/power-lines`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-OpenEphemeris-API-Key`
  - API key in header `X-API-Key`
  - API key in header `X-Service-Key`

Calculate strictly isolated ACG power lines (MC, IC, AC, DC). Options configurations to include aspects/midpoints will be explicitly stripped.

## Request body

- ACGRequestPayload: Primary payload structure for ACG global line calculation requests.
  - `bodies` string[]: Explicit body name selection. Supported: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto, Chiron, Pholus, Ceres, Pallas, Juno, Vesta, MeanNode, SouthNode, TrueNode, TrueSouthNode, MeanLilith, OscuLilith, Vertex, and the seven Hermetic lots Fortune, Spirit, Eros, Necessity, Courage, Victory and Nemesis. The eight Uranian (Hamburg School) hypothetical points (Cupido, Hades, Zeus, Kronos, Apollon, Admetos, Vulkanus, Poseidon) are accepted too, but only when named here: they are opt-in and never appear in a group's default roster. Fortune and Spirit are Hermetic lots and resolve only under a lot-bearing roster: `group: "hermetic"` or `group: "all"` (POST /acg/hermetic-lines pins that group itself, so it needs no `group`). Naming a lot under any other group is rejected with 422 rather than silently returning the default roster; on /acg/hits, where `hermetic`/`all` are Scale-tier, a lot named by a caller below that tier is rejected the same way. Aliases: NorthNode/Rahu/Node -> MeanNode; TrueNorthNode/TrueRahu -> TrueNode; Ketu -> SouthNode; Vulcanus -> Vulkanus. The extended catalog is accepted too, by name and only when named: the sb441 main-belt asteroids (Hygiea, Eunomia, Psyche, Europa (asteroid), Cybele, Sylvia, Thisbe, Camilla, Iris, Davida, Euphrosyne, Interamnia), the trans-Neptunian objects (Eris, Sedna, Makemake, Haumea, Quaoar, Orcus, Ixion, Varuna, Chaos, Gonggong, Salacia), the extra centaurs (Asbolus, Hylonome, Nessus, Chariklo) and about forty further asteroids (Eros (asteroid), Sappho, Lilith (asteroid), Fortuna, Pandora, Diana, Hekate and more) - GET /catalogs/bodies lists them all. The asteroid Eros is `Eros (asteroid)`: plain `Eros` is the Hermetic lot. Each extended body named adds 1 credit to the request (capped at +20); the standard roster, the Uranian set and the lots are covered by the base price. Extended bodies are never in a group's default roster.
  - `custom_bodies` ACGCustomBody[], nullable: Enterprise tier. Caller-supplied fixed points drawn like bodies: each `{id, name?, longitude/latitude or ra_deg/dec_deg, metadata?}` yields MC/IC/AC/DC lines (and aspect lines) at the coordinates given, with `id` and `metadata` echoed back. TOP-LEVEL field, a sibling of `bodies`. Up to 32 points, 1 credit each (with extended catalog bodies, capped at +20 per request). See the ACGCustomBody schema. Below Enterprise the request is refused with 403.
    - `dec_deg` number, double, nullable: Declination in degrees, -90 to 90. Equatorial frame: give with `ra_deg`.
    - `id` string, required: Your identifier for this point: 1-64 characters, letters, digits and `_ . : -`, starting with a letter or digit. Unique within the request (case-insensitive). Echoed as `custom_id`.
    - `latitude` number, double, nullable: Ecliptic latitude in degrees, -90 to 90. Optional, default 0. Ecliptic frame only.
    - `longitude` number, double, nullable: Ecliptic longitude in degrees, any real value (wrapped into [0, 360)). Ecliptic frame: give this and, optionally, `latitude`.
    - `metadata` object, nullable: Arbitrary JSON object, echoed back verbatim on every line and in `metadata.bodies`. At most 2048 bytes serialized. Never interpreted.
    - `name` string, nullable: Display label and `body_name` for this point. Defaults to `id`. Up to 64 characters.
    - `ra_deg` number, double, nullable: Right ascension in DEGREES (0-360, wrapped), not hours. Equatorial frame: give with `dec_deg`.
  - `epoch` string, required: ISO-8601 datetime of the birth or event. Either put the zone on the value itself as a 'Z' or ±HH:MM suffix ("1987-07-15T09:01:00-05:00"), or send the naive local wall-clock time ("1987-07-15T09:01:00") and name its zone in the sibling `timezone` field. A zone-less clock time with no `timezone` is rejected with 400 ambiguous_datetime and is NEVER read as UTC. A date-only value resolves to 12:00 UTC.
  - `format` string: Response format. `llm` returns compact rows + schema in metadata; only honored by /acg/hits.
  - `group` string, nullable: Body group selector. `standard` (default) = planets + asteroids; `hermetic` = Hermetic Lot lines (Fortune, Spirit, etc.); `all` = both; `hd` = the Human Design 13 (Sun, Earth, Moon, Mercury–Pluto, Mean Node, South Node) — pair with options.include_hd_gate for gate-labelled lines. The Hermetic lots are a Scale-tier feature: on the Developer-tier endpoints that accept this selector (/acg/hits, /acg/power-lines, /acg/ccg) a below-Scale caller has `hermetic`/`all` downgraded to the standard roster, and naming a lot in `bodies` is rejected with 422 rather than silently answered with the full roster. Hermetic lots require natal birthplace data.
  - `jd` number, double: Julian Day (alternative to epoch)
  - `natal` ACGNatalRequest: Natal geographical data for ACG offset calculation.
    - `birthplace_alt_m` number
    - `birthplace_lat` number: Birthplace latitude. Both birthplace coordinates must be supplied together -- a natal object with an incomplete pair is rejected rather than defaulting to 0,0. Distinct from the analysis target coordinates on the enclosing payload.
    - `birthplace_lon` number: Birthplace longitude. Both birthplace coordinates must be supplied together -- a natal object with an incomplete pair is rejected rather than defaulting to 0,0. Distinct from the analysis target coordinates on the enclosing payload.
    - `houses_system` string
  - `options` ACGOptionsRequest: Configuration options for AstroCartography calculations.
    - `angle_epoch` string: Decouple the rotational frame from the position epoch: body positions come from epoch/jd as usual, but ACG line angles are projected against this epoch's GMST. Accepts an ISO-8601 UTC datetime or a bare Julian Day. Empty/omitted = angles use the position epoch (default, unchanged). Use to overlay a secondary chart on a base frame — e.g. Human Design Design-register lines on the natal map (positions at the Design epoch, angles at the natal epoch), matching the hd_expression heatmap convention; also progressed/return overlays. Positions and obliquity stay on the position epoch, so every line is rigidly translated in longitude by the GMST difference.
    - `aspect_angles` number[]: Angles to compute aspects for
    - `asteroid_groups` ACGAsteroidGroup[]: Filter by asteroid group. Main belt and fixed stars are explicitly prohibited.
    - `include_aspects` boolean: Include aspect lines
    - `include_hd_gate` boolean: Enrich every emitted line feature with the Human Design gate its body's ecliptic longitude carries (properties.hd_gate: gate/line/color/tone/base). Purely additive — does not change the body set or geometry. Default false. Combine with bodies:["Earth"] or group:"hd" for the HD-13 body set.
    - `include_hd_lot_gates` boolean: With include_hd_gate, also attach the Human Design gate to Hermetic Lot lines (Fortune, Spirit, and the rest of the lot suite), computed from the lot's own ecliptic longitude in the personality register. Lots are left out of HD enrichment by default; no effect without include_hd_gate. Purely additive. Default false.
    - `include_lines` boolean: CCG only: emit MC/IC/AC/DC GeoJSON line geometry per snapshot (identical to /acg/power-lines, with ccg_hybrid progression applied per body). Default false. No effect on /acg/natal-lines.
    - `include_midpoints` boolean: Include planetary midpoint lines
    - `include_parans` boolean: Include parans (latitude crossings)
    - `line_types` string[]: Line types to include. Supported: MC, IC, AC, DC, ASP. Aliases: POWER -> MC+IC+AC+DC; ASPECT/SPECT -> ASP.
    - `paran_lat_cutoff` number, double: Maximum absolute latitude (in degrees) for paran crossing points. Crossings whose intersection latitude exceeds this value (north or south) are excluded from the response. When null or omitted, no cutoff is applied (current behavior preserved). Range: 0-90.
    - `refraction_correction` boolean: Apply atmospheric refraction to AC/DC
    - `resolution` integer: Resolution slices for mapping
  - `query_lat` number, nullable: Latitude of the query point
  - `query_lon` number, nullable: Longitude of the query point
  - `radius_deg` number, nullable: Proximity radius in degrees
  - `target_longitudes` ACGTargetLongitude[]: TOP-LEVEL field — a sibling of `bodies` and `options`, NOT nested inside `options`. Nesting it under `options` is silently ignored (unknown fields are dropped, so you get HTTP 200 with zero lines and no validation error). Synthetic points defined by arbitrary ecliptic longitudes rather than real bodies — e.g. the 12 zodiac sign cusps for chart-rotation ("relocation astrology": where would this degree sit on the AC/MC). Each produces MC/IC/AC/DC line geometry via the same math as a real body, filtered by `options.line_types` (that one IS under options). Lines are identified by target_longitude/label in properties rather than body_name. AC/DC use the geometric horizon (h₀ = 0) regardless of options.refraction_correction: a target longitude is a mathematical point with no light path to refract, and this keeps the line locked to the same definition the house engine uses for the Ascendant.
    - `label` string: Display label for this point, e.g. "Leo cusp". Defaults to "<Sign> cusp" derived from longitude when omitted.
    - `longitude` number, double: Target ecliptic longitude in degrees, any real value (wrapped into [0, 360) internally). Deliberately NOT marked `required`: 0 is a legitimate value (0° Aries), so an omitted field must be rejected by the handler rather than silently read as 0.
  - `timezone` TimezoneInput: Timezone input using IANA names or UTC offsets.
    - `fold_preference` 'earlier' | 'later': Which occurrence to use when the naive local datetime falls in a fall-back fold (a repeated hour): 'earlier' (default — first occurrence) or 'later'. Only meaningful for naive datetimes; the response reports datetime_status=ambiguous_fold either way so the ambiguity can be surfaced to the user.
    - `iana_name` string: IANA timezone name
    - `time_standard` 'auto' | 'standard' | 'daylight': How to interpret a naive local datetime when this zone is applied. 'auto' (default): resolve through the historical-correction overlay where one covers the region/era, then IANA tzdata. 'standard': force the zone's standard (non-daylight) offset — for callers who KNOW the recorded time was standard time regardless of what tzdata believes. 'daylight': force standard+1h. Forcing either marks the resolution tz_confidence=client_override. Ignored when the datetime carries its own Z/±HH:MM suffix or when utc_offset is used.
    - `utc_offset` number: UTC offset in hours

## Response `200`

FeatureCollection response (`features` is always an array; may be empty).

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/openephemeris/apis/open-ephemeris-api.md) · [All operations](https://skmtc.dev/openephemeris/apis/open-ephemeris-api/llms.txt) · [OpenAPI document](https://skmtc.dev/openephemeris/apis/open-ephemeris-api/revisions/d195a769cb89?raw)