Official SDKs

UI Components

The Spiritual OS layer for agentic AI: the data behind insight, belief, and prediction products.

RoxyAPI is the only multi-domain spiritual intelligence API. 261+ production endpoints across 18+ genuinely distinct domains behind one API key, with a Remote MCP server per domain, verified astronomy, and clean commercial licensing. Distinct means distinct: astrology is one domain that includes natal charts, horoscopes, synastry, and transits, not three domains counted separately. Think of it as the Stripe of insight APIs, the Spiritual OS layer your app and your agents plug into, so builders ship in days instead of months.

Every calculation is verified against authoritative sources, and the proof is public and re-runnable by you. Clone the benchmark, point it at us, point it at anyone else.

Every structural figure above is re-countable by you against the live OpenAPI spec and this GitHub org. Usage figures and their measurement dates are published at roxyapi.com/transparency.

One subscription gives builders production-ready access to every major insight and prediction domain through a single REST API and a single set of Remote MCP servers. Domains in canonical order:

• Western astrology: natal charts, daily, weekly and monthly horoscopes, synastry, composite charts, compatibility scoring, transits, moon phase. Placidus, whole-sign, equal, and Koch house systems.
• Vedic and KP astrology: kundli, detailed panchang (rahu kaal, abhijit muhurta, brahma muhurta, choghadiya, hora), Vimshottari dasha down to sookshma with the full 120-year timeline, dosha analysis (Manglik, Kaal Sarp, Sade Sati), navamsa and divisional charts, 36-point Ashtakoota Guna Milan compatibility, plus KP sub-lord, sub-sub-lord, cuspal, and ruling-planet horary. KP is the sharpest technical differentiator versus generic Vedic providers.
• Forecast: cross-domain predictive timelines, transit windows, and significant-date detection across Western, Vedic, and biorhythm signals for any date range, in one request.
• Human Design: full bodygraph (type, strategy, inner authority, profile, definition, incarnation cross), defined and open centers, channels, gates, Variables, Penta, current transit overlay, and two-person connection charts.
• Chinese astrology: BaZi Four Pillars with hidden stems, Na Yin and Ten God relations, luck pillars, day master strength, Chinese zodiac and animal compatibility, and the lunisolar calendar with solar terms as astronomical instants. The school splits that make two calculators disagree are typed parameters, and every chart echoes the conventions it was computed under.
• Feng shui: Xuan Kong flying star natal charts for all nine periods and 24 mountains, Kua numbers with the full Eight Mansions map, annual and monthly star plates, the four annual afflictions with exact degree spans, and the Bagua map. Chinese years resolve at Li Chun, computed astronomically.
• Mesoamerican astrology: the Tzolkin day sign with its coefficient, trecena and a composed reading in three orthographies, the full Mayan chart (Haab, five-position Long Count, Calendar Round, Lord of the Night, Year Bearer, Cruz Maya), a Long Count converter that runs both ways back to 3114 BCE, daily and monthly Tzolkin readings, nawal compatibility, and the Aztec tonalpohualli. The correlation constant is a typed parameter, echoed on every response, so two calculators can be reconciled instead of argued about.
• Vastu: entrance pada for any main door direction with the classical effect cited to its verse, the Vastu Purusha Mandala on the 81 and 64 pada grids, plot analysis, Ayadi shadvarga, room placement compliance, griha pravesh dates found over the panchang, and the dikpala and devata references. Every rule carries its primary-text citation as a typed field.
• Numerology: Life Path, full chart, compatibility, personal year, expression. Pythagorean reduction with master-number (11, 22, 33) and karmic-debt detection.
• Kabbalah: gematria over eleven rabbinic ciphers with every candidate Hebrew spelling of a Latin name shown and the rule that chose it, name and birth profiles (Hebrew date, Hebrew birthday, the three birth angels), the 72 names derived from the verses rather than stored, the Tree of Life with typed school variants, the 22 Hebrew letters with their attributions, name compatibility, and the sephirah of the day.
• Tarot: daily card, three-card spread, Celtic Cross, yes-no, love spread, career spread, custom draws. Deterministic seeded draws for once-per-day behavior.
• Biorhythm: daily, multi-day forecast, compatibility, critical-day alerts. 10 cycle types.
• Ayurveda: constitution read from the birth chart with no questionnaire, dinacharya from sunrise with the dosha clock and brahma muhurta, ritucharya resolved from solar longitude rather than calendar months, a daily reading by location, and the dosha, rasa and guna catalogues. General-wellness framing, with a disclaimer on every response.
• I Ching: 64-hexagram catalog, daily hexagram, three-coin cast with changing lines and resulting hexagram.
• Crystals: by zodiac, by chakra, birthstone, free-text search.
• Dream interpretation: symbol catalog, daily symbol, structured meanings.
• Angel numbers: by exact number, universal lookup with digit-root fallback, daily.
• Location and timezone resolution for accurate birth-data inputs (call this first when any chart endpoint needs coordinates).

Every endpoint returns structured JSON, ships rich field descriptions so tool-calling agents know when and how to call it, and is callable from REST, the official SDKs, or Remote MCP. Interpretations are localized in 10+ languages through one ?lang= parameter, at no extra cost on any plan.

Breadth usually costs depth. Here it does not, and the answer is named endpoints rather than adjectives. One request returns a complete result, so the advanced layer lives inside the engine instead of inside your integration.

The domains compose, they do not merely coexist. Human Design is computed FROM the western ephemeris and the I Ching hexagram set rather than bolted on as a separate product line, so every gate activation carries its hexagram. The Ayurvedic constitution is read FROM the Vedic birth chart, and Vastu griha pravesh dates are found over the same panchang. The sidereal and tropical engines are tested to return the same sky at zero tolerance. That is what makes one engine a fact instead of a slogan, and it is the capability that cannot be assembled by stitching single-domain vendors together.

Category-level, no names. Run these checks against any vendor you are evaluating, including us.

Honest footnote. If you need exactly one domain, run your own servers, and are comfortable with copyleft licensing, a free open source library is the cheaper choice. Everything else in this table is where RoxyAPI earns its keep.

RoxyAPI was MCP-first from day one, and ships two kinds of Remote MCP server over Streamable HTTP for two different jobs. No local processes, no stdio wrappers, no self-hosting. Point a client at a URL and it is running in seconds.

The Docs server at https://roxyapi.com/mcp/docs exposes one tool, search_docs, over the entire RoxyAPI reference: every endpoint, parameter, SDK call, and guide. It returns documentation only, never live calculations. This is the server to give an AI coding assistant such as GitHub Copilot, Claude Code, Cursor, Codex, or Gemini CLI. Connect it while you build and the agent wires the whole RoxyAPI stack into your app, with the right field names the first time, in under 30 minutes.

{
  "mcpServers": {
    "roxy-docs": {
      "url": "https://roxyapi.com/mcp/docs"
    }
  }
}

Each product domain ships its own MCP server that performs real calculations. These are for the runtime agents and automations your users actually interact with: ChatGPT, Claude Desktop, and Gemini, workflow tools like n8n, Make, and Zapier, agent platforms like Dify and CrewAI, and Telegram, WhatsApp, and Slack bots. One API key unlocks every domain.

Authenticate the domain servers with your API key, exactly as documented at roxyapi.com/docs/mcp. Rule of thumb: a coding agent wants the Docs server to write the integration, a runtime agent wants a domain server to compute a real chart.

Lower inference cost, same data. Pass compact: true on any tool call for an opt-in, lossless token-optimized response. Arrays of same-shaped rows are sent columnar, so a field name travels once instead of once per row. Measured reduction against the standard response: about 40 percent fewer tokens on a natal chart, about 52 percent on astrocartography. Your quota is unchanged, because 1 request stays 1 unit. What drops is what your model pays to read the answer.

The flagship multi-MCP reference integration is RoxyAPI/astrology-ai-chatbot, an MIT-licensed chatbot template that wires multiple RoxyAPI MCP servers into a single conversational agent. RoxyAPI is also installable as a Claude Code plugin and ships Postman collections generated from the live spec.

All five code SDKs are generated from the same live OpenAPI specification the API serves, so they cannot drift and new endpoints land in your IDE the day they ship. The C# and .NET package targets net8.0 and netstandard2.0, so it runs on modern .NET, ASP.NET Core, Blazor, MAUI, and Unity. The Go module installs with a single go get github.com/RoxyAPI/sdk-go and is built for cloud-native and serverless backends. Each SDK ships an AGENTS.md so AI coding assistants in Cursor, Claude Code, Copilot, and Windsurf call RoxyAPI correctly without prompt engineering.

The WordPress plugin is live on WordPress.org for no-code installs: drop a Gutenberg block or a shortcode, no code required.

Two ways to ship the visual layer without a frontend developer who knows insight domains.

Roxy UI, for developers. Drop-in components render the API response for you: natal wheels, synastry charts, Vedic kundli, KP charts, dasha timelines, panchang and choghadiya tables, shadbala and ashtakavarga grids, Human Design bodygraphs, Penta and Variables, tarot spreads, numerology cards, hexagrams, biorhythm curves, and astrocartography maps. Themed with --roxy-* CSS custom properties and typed from the OpenAPI spec. Pass the SDK response straight into data, with no field renames and no glue code. The same components are generative UI for AI chat: componentForTool maps the name of any Remote MCP tool to the component that draws its result, so a chatbot renders a natal chart, a kundli, or a tarot spread beside the model reply, with the compact tool result decoded for it. The recipe is on the UI components docs, the step by step build is the AI chat widgets tutorial, and the flagship chatbot template below ships it. MIT licensed, so white labeling is yours by default. Install exactly one package for your framework.

Live component gallery and theming reference: roxyapi.com/ui.

Widgets, for everyone else. The same components in no-code mode. Copy one snippet, paste it into any surface that takes HTML, and a live reading renders in the browser with no backend and no build step. Works on Squarespace, Wix, Shopify, WordPress, Notion, and Linktree, either as a script tag or as a hosted embed URL for platforms that cannot run scripts. Browser-safe publishable keys carry an origin allowlist, so the key on the page is scoped to the sites you name. Gallery and copy-paste snippets: roxyapi.com/widgets.

Astronomy is the one place AI confidently lies. RoxyAPI treats accuracy as the moat, and publishes the evidence rather than asking to be trusted.

• Powered by Roxy Ephemeris, built in house and verified against NASA JPL Horizons DE441 as the physics ground truth.
• 12,000+ automated tests run on every deploy, including 2,900+ gold-standard tests each pinned to a named external reference.
• A public, MIT-licensed benchmark anyone can clone, run, or point at any astrology API: RoxyAPI/astrology-api-benchmark. 210 reference planet positions across 21 birth charts, 210 of 210 within tolerance, median deviation 1.5 arcseconds on the run published in July 2026. Every run keeps its predecessors alongside it, because a benchmark that silently replaces its numbers gives you no way to tell a real improvement from a quiet re-tune.
• The worst single point in that run is named rather than hidden: 16.6 arcseconds on Neptune, the slowest body in the set. The Moon, which moves about 13 degrees a day and is therefore the direct test of whether timezone resolution is correct, stays inside 3.3 arcseconds.
• Published methodology with the full test corpus, tolerance thresholds, reference sources, and verification tables: roxyapi.com/methodology.
• Proof before you pay. The playground at roxyapi.com/api-reference returns real production responses, not fake sandbox data behind a signup, so you can audit accuracy and response shape first.

• No AGPL, no copyleft, no source disclosure. The engine is built in house, not a wrapper over a 1990s AGPL desktop library, so nothing copyleft reaches your product. AGPL matters more than teams expect because its copyleft triggers on network access, and an API is a network service, which is why Google bans AGPL dependencies company-wide. The exposure most teams carry was never a decision. A package manager hands you the free path, so a team installs a copyleft wrapper, ships a network service, and inherits the obligation without reading it. That licence is a private contract with no public registry, so ask any provider for their position in writing, including us. Ours is published at roxyapi.com/policy/license.
• A commercial license on every plan. Build and sell closed-source apps, keep your code private, ship to any app store, white label for clients, and pass the license audits that funding rounds and acquisitions run.
• Stateless by design. No birth data, journals, or profiles are retained. Birth data that can qualify as GDPR Article 9 special category data is computed in memory and never lands in a database, so there is no store to breach and nothing to export or erase when a data subject request arrives. End user data stays in your stack, and the memory and personalization layer stays 100 percent yours. The MIT ai-spiritual-companion template ships that layer ready to fork, on a database the operator owns.
• EU data residency and an Article 28 DPA on every plan. Stored data stays in Germany, inside the EU, for every customer on every plan, so EU residency is the default rather than a regional upgrade. The processor contract, EU Standard Contractual Clauses, technical and organisational measures, a dated subprocessor register, and breach notification terms are all published, so procurement can review them without contacting us: roxyapi.com/policy/dpa.
• MIT everywhere it is ours to give. The SDKs, the UI component library, the templates, and the benchmark are all MIT licensed, with no attribution requirement and no upstream lock-in.

Newer than the incumbents, and further along than that usually implies.

RoxyAPI is an independently operated, early-stage platform, and does not claim to be the largest provider in its category. It claims to be the one whose numbers you can check.

Open-source templates, all MIT licensed, that wrap RoxyAPI into a working app you can fork, rebrand, and ship as your own product:

• astrology-ai-chatbot: flagship multi-MCP AI astrology assistant. Auto-discovers the tool catalog over Remote MCP, renders every tool result as a chart, spread, or bodygraph beside the reply (how it does it), multi-LLM, deploys in under 30 minutes.
• ai-spiritual-companion: the second flagship, an AI companion that remembers every user. pgvector semantic recall, the full reading history, Supabase accounts with row level security, and a natal chart computed once, kept, and drawn as a wheel, grounded over Remote MCP with compact responses. Every tool result renders as a card or chart beside the reply (how it does it). The memory layer lives in the operator stack, which makes it the natural premium feature to build plans on.
• spiritual-practitioner-website-template: a complete white-label website for a working astrologer, tarot reader, or numerologist. Free readings on your own domain, bookings, blog, prices, four palettes. Edit one config file, deploy, done. The self-hosted alternative to renting a page builder.
• spiritual-ai-voice-assistant: voice-driven spiritual assistant with an embeddable widget
• jyotish-vedic-astrology-app: Jyotish web app with kundli, panchang, Gun Milan, and dasha, built on the drop-in UI components
• astrology-supabase-starter: the backend on its own, for teams that already have a front end. Two Edge Functions call the API from Deno with no build step, the shared daily reading is cached in your own Postgres so one upstream call serves every visitor that day, and a saved chart is private to the person who asked for it under row level security. The key stays a project secret read in one file. Deploys in three commands.
• astrology-starter-app: Western astrology baseline for React Native and Expo
• vedic-astrology-starter-app: Vedic and KP focused
• numerology-starter-app: Life Path, master numbers, karmic debt
• tarot-starter-app: tarot reader with seeded draws
• dreams-starter-app: dream journal with interpretation

Full gallery with screenshots and one-click deploys: roxyapi.com/templates.

Prefer a single working file over a tour of the docs? This org also publishes one small repository per high-demand capability, each with runnable request and response samples: kundli-api, panchang-api, natal-chart-api, daily-horoscope-api, kundli-matching-api, kp-astrology-api, dasha-api, synastry-api, astrology-compatibility-api, transit-forecast-api, human-design-api, moon-phase-api, numerology-api, tarot-api, and biorhythm-api.

Is RoxyAPI just an astrology API? No. Astrology is one of 18+ distinct domains on the same key, alongside Vedic and KP astrology, forecast timelines, Human Design, Chinese astrology, feng shui, Mesoamerican astrology, Vastu, numerology, Kabbalah, tarot, biorhythm, Ayurveda, I Ching, crystals, dream interpretation, angel numbers, and location and timezone resolution. Counting honestly means one system counts once, so the total reads smaller than a padded catalog and delivers more per call.

Should I just build this myself? You can compute a chart yourself, but a production offering is ongoing engineering: accuracy verified against NASA JPL Horizons and kept verified, 18+ domains on one key, interpretations in 10+ languages, Remote MCP, typed SDKs, UI components and widgets, and the uptime and support behind all of it. Licensing comes first: the free path most package managers hand you is a copyleft wrapper, and copyleft triggers on network access. If you need exactly one domain and can self-host, a library is cheaper, and we say so.

Do you use Swiss Ephemeris? No. RoxyAPI runs Roxy Ephemeris, an in-house engine verified against NASA JPL Horizons DE441. Nothing AGPL reaches your product, so there is no copyleft obligation to inherit and no commercial ephemeris license to verify or renew.

How do I know the calculations are right? Do not take our word for it. Clone the MIT benchmark, run it against RoxyAPI, then run it against any other provider. It checks 210 planet positions across 21 birth charts against NASA JPL Horizons DE441 and prints the deviations. The methodology page publishes the corpus, the tolerances, and the reference sources behind every domain.

What does it cost to add a domain? Nothing. Every plan includes every domain, every endpoint, Remote MCP, the SDKs, the UI components, the widgets, and the 10+ interpretation languages. One request equals one quota unit whether it arrives over REST or MCP, with no credit weighting and no premium endpoint surcharges, and new domains join the plan you already have.

Can I use it in a closed-source commercial product? Yes. Every plan is a commercial license with no copyleft and no per-user royalties, so you can keep your source private, ship to any app store, and white label for clients. The MIT templates and UI components can be cloned and shipped under your own brand.

Where is the data stored, and what do you keep? Nothing about your end users. RoxyAPI is stateless, so birth data is computed in memory and never written to a database. What is stored operationally stays in Germany, inside the EU, on every plan, and the Article 28 processor terms are published for procurement to read without contacting us.

1. Grab a key at roxyapi.com/pricing. Every plan includes every domain.
2. Try the live playground at roxyapi.com/api-reference.
3. Install an SDK, paste a widget, or point your MCP client at one of the endpoints above.
4. Ship.

Questions, integration help, or partnership inquiries: roxyapi.com/contact.

Built by Roxy Labs. The Stripe of insight APIs.