How to Build an Astrology App with RoxyAPI - Developer Guide 2026

TL;DR

RoxyAPI gives you 8 spiritual intelligence domains under one API key: Western astrology, Vedic astrology, tarot, numerology, I-Ching, crystals, angel numbers, and dreams
A working birth chart response requires date, time, latitude, longitude, and a UTC offset
The Model Context Protocol (MCP) integration lets AI agents call astrology endpoints directly without writing integration code
First API call in under 30 minutes using the starter guide or pre-built starter apps

About the author: Brett Calloway is a Developer Advocate and AI Integration Specialist with 12 years of experience building APIs and developer tooling. He has led developer relations at two Series B SaaS companies and spoken at PyCon and JSConf on building AI agents with Model Context Protocol.

What You Will Build

This guide walks through making your first calls to the RoxyAPI astrology and numerology endpoints. By the end, you will have a working birth chart response from the Western astrology API, a Vedic chart with nakshatra data, and a full numerology profile, all from the same API key. The API follows standard REST conventions: HTTPS, JSON request bodies, and a single X-API-Key header for authentication. There is no OAuth flow, no token refresh, and no regional routing. One key works on all endpoints across all eight domains.

Getting Your API Key

Subscribe at roxyapi.com/pricing and your API key is delivered immediately by email. The key follows the format {uuid}.{hex}.{base64} and is passed in every request as an X-API-Key header. There is no sandbox mode because the API is deterministic: the same input always returns the same output, so you can test freely against production without worrying about side effects. The interactive API reference at roxyapi.com/api-reference lets you try every endpoint directly in the browser before writing a single line of code.

Your First Western Astrology Call

The natal chart endpoint accepts date, time, latitude, longitude, and timezone offset and returns sun sign, moon sign, rising sign, and all planetary positions. A typical request looks like this:

curl -X POST https://roxyapi.com/api/v2/astrology/natal-chart \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"1990-06-15","time":"14:30:00","latitude":40.7128,"longitude":-74.0060,"timezone":-4}'

The response includes sun, moon, and rising signs, house cusps, and positions for Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto. All positions use the tropical zodiac with Placidus houses by default. Sidereal calculations and alternative house systems are available via query parameters.

Adding Vedic Astrology and Nakshatra Data

The Vedic astrology endpoint accepts the same input format. Switching from Western to Vedic is a matter of changing the URL path. The Vedic response adds nakshatra, pada, nakshatra lord, and the current Vimshottari dasha period. For KP astrology specifically, the kp-birth-chart endpoint returns sub-lords for all house cusps and planets using the Krishnamurti Paddhati system.

Ready to ship? RoxyAPI covers Western astrology, Vedic astrology, tarot, numerology, I-Ching, crystals, angel numbers, and dreams under one subscription. Clone a starter app to skip the boilerplate entirely. See pricing.

AI Agents and Model Context Protocol

If you are building with an AI assistant like Claude, GPT-4o, or Gemini, RoxyAPI exposes all endpoints as MCP tools. Adding the MCP server to your agent configuration lets the model call birth chart, tarot, and numerology endpoints as native function calls without any integration code on your side. The MCP setup guide is at roxyapi.com/docs/mcp. This approach is particularly useful for AI-powered report generation, where the model grounds its interpretive output in live computed data rather than training memory.

Frequently Asked Questions

Q: Does RoxyAPI support all eight spiritual domains on every plan? Yes. Every subscription tier, including the Starter plan, includes access to all eight domains: Western astrology, Vedic astrology, tarot, numerology, I-Ching, crystals, angel numbers, and dreams. There is no feature gating by domain and no add-on pricing for specific endpoints.

Q: What timezone handling does the API use? You pass the local date and time along with a UTC offset. The API handles the conversion internally. There is no need to convert to UTC before sending the request. For historical dates or locations with non-standard offsets, pass the offset that was in effect at the time and place of the event.

Q: Can I use RoxyAPI with no-code tools like Bubble or Wix? Yes. The REST endpoints work with any HTTP client including Bubble API Connector, Wix Velo wix-fetch, Make HTTP modules, and Zapier webhooks. The API reference includes example request shapes you can paste directly into most no-code HTTP connectors.

Q: Is there a rate limit during testing? Rate limits apply per subscription tier by monthly request quota, not by per-second rate. There is no separate burst limit for development usage. If you exhaust your monthly quota while testing, you can upgrade your plan or contact support for a temporary reset.