Western Composite
asterwise_get_western_composite
Midpoint composite chart for two people. Each composite planet is the midpoint of the two natal positions. Returns composite planets with dignities and internal aspects.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
person1 | object | yes | Birth data for Western astrology tools (tropical zodiac). Fields: date, time, lat, lon, person_name, timezone, house_system |
person2 | object | yes | Birth data for Western astrology tools (tropical zodiac). Fields: date, time, lat, lon, person_name, timezone, house_system |
response_format | enum: markdown, json | no |
What it covers
Single synthetic chart representing the relationship as its own entity — not person A vs person B overlaid. Midpoints handle wrap-around at 360° correctly.
Workflow
BEFORE: asterwise_get_western_synastry — examine inter-chart aspects before composite.
AFTER: None.
Input
person1, person2 — WesternBirthData each. house_system ignored.
Output contract
data.planets[] — 10 composite planets with name, longitude, sign, degree_in_sign, dignity, dignity_score
data.ascendant_longitude, data.ascendant_sign, data.ascendant_sign_index
data.aspects[] — internal aspects within the composite chart
Response format
response_format=json serialises the complete response as indented JSON.
response_format=markdown renders the same data as a human-readable report.
Both modes return identical underlying data.
Compute class
MEDIUM_COMPUTE (~600ms)
Errors
INVALID_PARAMS (local): WesternBirthData validation failures.
INTERNAL_ERROR: Any upstream API failure or timeout → MCP INTERNAL_ERROR
Do not confuse with
asterwise_get_western_synastry — two charts, inter-chart aspects vs composite (one midpoint chart).
asterwise_get_western_compatibility — numeric score vs structural composite chart.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.