Western Weekly Transits
asterwise_get_western_transits_weekly
7-day transit window vs natal chart. Returns day-by-day transit snapshots plus peak aspects (active 4+ days in the window). Use start_date to set the week start; defaults to today.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
birth | 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 | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
start_date | string/null | no | Start of the window, YYYY-MM-DD. Defaults to today when omitted. |
What it covers
Rolling seven-day transit analysis with one snapshot per day (same structure as daily transits) plus peak_aspects highlighting aspects that persist across multiple days.
Workflow
BEFORE: asterwise_get_western_natal.
AFTER: asterwise_get_western_transits_monthly — for full month.
Input
birth — WesternBirthData. house_system ignored.
start_date (optional YYYY-MM-DD) — week start; defaults to today.
Output contract
data.start_date, data.end_date
data.days[] — 7 daily transit objects (same shape as daily transits)
data.peak_aspects[] — aspects active on 4 or more days
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 (~2s for 7 days)
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_transits_daily — single day.
asterwise_get_western_transits_monthly — 30 days vs 7.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.