Western Zodiac Compatibility
asterwise_get_western_zodiac_compatibility
Sign-to-sign compatibility without birth data. Based on element and modality affinity. Fast — no ephemeris calculation required.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
sign1 | string | yes | |
sign2 | string | yes | |
response_format | enum: markdown, json | no |
What it covers
Lookup table compatibility using sign elements (fire/earth/air/water) and modalities (cardinal/fixed/mutable). No houses, no Moon phase, no Venus Mars geometry.
Workflow
BEFORE: None — no birth data needed.
AFTER: asterwise_get_western_compatibility — when full charts are available.
Input
sign1, sign2 — English zodiac names (Aries … Pisces).
Output contract
data.sign1, data.sign2
data.element1, data.element2
data.modality1, data.modality2
data.element_affinity, data.modality_affinity — 'harmonious'|'neutral'|'challenging'
data.overall_score (int 0-100)
data.description (string)
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
FAST_LOOKUP — no ephemeris, pure table lookup.
Errors
INVALID_PARAMS (local): None — sign validation upstream.
INTERNAL_ERROR: Any upstream API failure → MCP INTERNAL_ERROR
Do not confuse with
asterwise_get_western_compatibility — requires full birth data, more accurate.
asterwise_get_western_synastry — aspect geometry between two full charts.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.