
AI Spiritual Voice Assistant
Web App / Open Source30 minTalk to the stars. Real readings across every spiritual domain, spoken aloud.
Ship a cross-domain forecast your users can plan around. This week.
Transit ForecastForecast TimelineSignificant Dates …and so much more
Want to try without writing code? Try this domain live in API playground →
npm install @roxyapi/sdkimport { createRoxy } from '@roxyapi/sdk'
const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.forecast.get(/* ... */)pip install roxy-sdkfrom roxy_sdk import create_roxy
roxy = create_roxy("your-api-key")
result = roxy.forecast.get(...) # async: await roxy.forecast.get_async(...)composer require roxyapi/sdkuse function RoxyAPI\Sdk\createRoxy;
$roxy = createRoxy(getenv('ROXY_API_KEY'));
$result = $roxy->forecast->get(/* ... */);dotnet add package RoxyApi.Sdkusing RoxyApi;
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
// await roxy.Forecast.<resource>.GetAsync() or .PostAsync(new() { ... })go get github.com/RoxyAPI/sdk-goimport roxyapi "github.com/RoxyAPI/sdk-go"
roxy, _ := roxyapi.NewRoxy(os.Getenv("ROXY_API_KEY"))
// resp, err := roxy.Forecast.<Method>(context.Background(), nil)curl -H "X-API-Key: YOUR_KEY" \
https://roxyapi.com/api/v2/forecast/claude mcp add --transport http \
roxy-forecast https://roxyapi.com/mcp/forecast \
--header "X-API-Key: YOUR_KEY"AI agents auto-discover all endpoints as callable tools. Zero configuration.
Want to ship faster? Clone a free template and go from zero to production in 30 minutes.
Building with Cursor, Claude Code, or Bolt? Use our AI prompts to generate a complete app in minutes.
Building on WordPress? Install the RoxyAPI plugin and drop a shortcode, no code required.
{
"birthData": {
"date": "1990-07-15",
"time": "13:30:00",
"timezone": 5.5,
"latitude": 0,
"longitude": 0
},
"startDate": "2026-01-15",
"endDate": "2026-04-14",
"count": 7,
"events": [
{
"date": "2026-01-26",
"datetime": "2026-01-26T11:17:04Z",
"domain": "western",
"type": "sign-ingress",
"body": "Neptune",
"target": "Aries",
"description": "Neptune enters Aries, beginning a new sign cycle.",
"significance": 82
},
{
"date": "2026-01-28",
"datetime": "2026-01-28T07:48:19Z",
"domain": "western",
"type": "transit-aspect",
"body": "Saturn",
"target": "Black Moon Lilith",
"aspect": "trine",
"orb": 0,
"description": "Transiting Saturn trine natal Black Moon Lilith, an exact aspect within 0 degrees.",
"significance": 100
},
{
"date": "2026-02-03",
"datetime": "2026-02-03T11:34:59Z",
"domain": "western",
"type": "retrograde-station",
"body": "Uranus",
"station": "direct",
"description": "Uranus stations direct, releasing forward motion in its themes.",
"significance": 80
},
{
"date": "2026-02-07",
"datetime": "2026-02-07T20:00:00Z",
"domain": "vedic",
"type": "dasha-change",
"body": "Sun-Venus Antardasha",
"description": "Vimshottari Venus Antardasha begins within the Sun Mahadasha, shifting the active sub-period.",
"significance": 74
},
{
"date": "2026-02-13",
"datetime": "2026-02-13T23:37:58Z",
"domain": "western",
"type": "sign-ingress",
"body": "Saturn",
"target": "Aries",
"description": "Saturn enters Aries, beginning a new sign cycle.",
"significance": 82
},
{
"date": "2026-03-20",
"datetime": "2026-03-20T01:16:53Z",
"domain": "western",
"type": "transit-aspect",
"body": "Uranus",
"target": "Black Moon Lilith",
"aspect": "opposition",
"orb": 0,
"description": "Transiting Uranus opposition natal Black Moon Lilith, an exact aspect within 0 degrees.",
"significance": 100
},
{
"date": "2026-04-08",
"datetime": "2026-04-08T09:16:59Z",
"domain": "western",
"type": "transit-aspect",
"body": "Saturn",
"target": "Mercury",
"aspect": "trine",
"orb": 0,
"description": "Transiting Saturn trine natal Mercury, an exact aspect within 0 degrees.",
"significance": 100
}
]
}Structured JSON with documented fields. Not hallucinated text. See all endpoints
Works with your stack
Merge upcoming transit aspects, sign ingresses, retrograde stations, new and full moons, biorhythm critical days, and Vimshottari dasha changes into one time-ordered forecast for a single subject. The only cross-domain forecast timeline behind one key, positions verified against NASA JPL Horizons, available over Remote MCP with typed SDKs. Horizon capped at 90 days.
Every Forecast calculation is verified against NASA JPL Horizons across 828 gold-standard tests, with a public MIT benchmark repo anyone can clone and re-run. See how we test.
Multi-language API responses
Everything you need from our Forecast API, built for production:
One merged timeline across three engines: western transit-to-natal aspects, sign ingresses, retrograde stations, eclipses, and new and full moons, biorhythm critical days, and vedic Vimshottari mahadasha, antardasha, and pratyantardasha boundaries
Single subject per request and one forecast per response, a stateless bounded forecast rather than an open-ended batch scan
Server-clamped 90 day horizon and a 200 event cap, with the highest-significance events surviving the cap
Every astronomical event refined to its exact instant by search, not reported at a coarse daily sample point
Significance scoring from 0 to 100 so outer-planet exact aspects and mahadasha changes rank above fast Moon events and critical days
Selectable domains: request the full cross-domain merge, a western-only transit forecast, or just the high-significance dates
Click any endpoint to view detailed documentation, parameters, and response examples.
Render Forecast responses without building charts yourself. These open source, framework-agnostic web components take the typed API response and draw it, in React, Vue, Svelte, Angular, plain HTML, and WordPress.
| Element | Renders |
|---|---|
| <roxy-forecast-timeline> | Date-grouped events across Western, Vedic, and biorhythm domains, weighted by significance |
| <roxy-forecast-digest> | Per-window event counts, domain breakdown, and the highest-significance events |
Clone. Edit. Ship. Free and open source by Team Roxy.

Talk to the stars. Real readings across every spiritual domain, spoken aloud.
Browse all templates or use AI prompts to generate a custom app.
Real-world applications and use cases for integrating Forecast API into your projects:
Spiritual and self-discovery apps: a forward-looking what is coming digest that blends astrology and biorhythm in one call
AI chatbots and coaching assistants: significant-date awareness via remote MCP tool calls for timing conversations
Wellness and mindfulness platforms: critical-day and transit alerts for planning demanding or restful periods
Calendar and planner integrations: a time-ordered event stream ready to drop onto a date strip or notification feed
Astrology and Vedic practitioner tools: upcoming transits, stations, and dasha boundaries for one client at a time
Content and editorial platforms: significant upcoming dates for forecast columns and personalized timing pages
Dhani M.
Indie App Developer
Shipped an astrology app over a long weekend. Birth charts, nakshatras, KP cusps, significators. I verified the Lahiri ayanamsha values independently and they line up with my reference. One API key for all of it.
Tom H.
Senior Developer
The OpenAPI spec is the most complete I have seen in this space. Generated a type-safe TypeScript client from it in seconds. Every field has descriptions and examples. Production-grade documentation.
Chris W.
Backend Engineer
Response times consistently under 50ms for numerology and tarot endpoints. The API returns structured JSON with every field documented. Integrated it into our platform in an afternoon.
Every page here is built so AI search engines can read and cite it, so go straight to the source. Let ChatGPT, Perplexity, or Claude search the web and tell you what they find about RoxyAPI accuracy, MCP, SDKs, and pricing.
Opens a live web search in a new tab.
From zero to production in 3 steps. No signup required for testing.
Your agent grounds every answer in verified calculations and replies in your own voice, so it never hallucinates a chart, date, or reading. No local setup, no AGPL, no hosted-AI markup.
| 1Install the SDK | npm i @roxyapi/sdk |
| 2Get your API key | View Plans |
| 3Make your first call | View Docs |
Remote MCP, llms.txt, and AGENTS.md. The full agent-readiness stack for 12 spiritual domains under one key.
The forecast API returns a clean transit forecast for any birth chart over the days ahead: transiting planet to natal aspects, sign ingresses, retrograde and direct stations, eclipses, and new and full moons, each one placed at its exact instant rather than a rough daily sample. Every event carries a significance score from 0 to 100, so an outer planet aspect ranks above a passing Moon event and your feed leads with what matters. Positions come from Roxy Ephemeris, verified against NASA JPL Horizons. One key also unlocks eleven more spiritual data domains, with instant activation and flat pricing.
This is the standout. A single call merges Western transits, Vedic Vimshottari dasha periods, and biorhythm critical days into one time ordered, significance scored timeline that no single domain service ships. You get the whole picture of what is coming for a person in one response, ready to drop onto a date strip or notification feed. Start with the natural call for the full merge, then narrow to the engines you want or raise the significance floor to trim noise. Call it from the typed SDKs for TypeScript, Python, or PHP, or from our Remote MCP server with no local setup and no Docker.
The forecast API can return just the high significance turning points from the merged timeline: rare outer planet aspects, slow planet sign ingresses, retrograde stations, eclipses, and major Vimshottari dasha changes. Significance runs from 0 to 100, so the big shifts outrank the everyday ones and the result reads like a curated astrological calendar rather than a firehose. That makes it ready for timing alerts, year ahead pages, and at a glance forecast strips. Drop it onto a WordPress site with our plugin, or wire it up with our UI components.
Ask the timeline for the Vedic engine and it marks the exact boundaries where each Vimshottari mahadasha, antardasha, and pratyantardasha period begins inside your window. Each boundary names the period and carries a significance score, so a major mahadasha shift ranks above a faster sub period change. Because it is the same cross domain call, those dasha dates interleave with Western transits and biorhythm critical days in one sorted timeline behind a single key. Agents can pull the same data through our Remote MCP server, and an AGENTS.md and llms.txt make the whole catalog easy for tools to discover.
The forecast API surfaces the new moon and full moon for your window, each refined to its exact instant and tagged with its sign, alongside eclipses classified as penumbral, partial, annular, or total. They arrive inside the same timeline as your transits and dasha dates, so a lunar calendar and a personalized forecast come from one request. Every instant is computed by Roxy Ephemeris and verified against NASA JPL Horizons. The descriptions localize across eight languages while the underlying event types stay stable, so you can branch on them safely.
The forecast API casts a solar return for the exact moment the Sun returns to its natal position, the foundational technique for annual birthday and year ahead readings. It returns the full chart with planetary positions, house cusps, aspects, the Ascendant, and the Midheaven. Anchor it to the birthplace, or pass the current location for a relocated solar return where the houses shift to where the person spends their birthday. It is one of twelve domains behind a single key, callable from the typed SDKs and our Remote MCP server, with positions verified against NASA JPL Horizons.
Ship a cross-domain forecast your users can plan around. This week.
All 12 domains included with every plan. Every endpoint, MCP server, SDK, and starters.
Plans from $39/mo — thats $3.25 per domain. No credit card required for testing.
View Pricing & Get API KeyHi, I'm Rosie, your guide to RoxyAPI's insight tools.
Ask me to read your birth chart, pull a card, or map your numbers, and I'll interpret what it means for you. Unlike most AIs, I never make the numbers up: every reading runs on real, verified calculations. Curious about the API, pricing, or docs instead? Ask me that too.