Remote MCP on the 2026-07-28 specification, plus a stdio relay
Every Remote MCP server speaks the stateless 2026-07-28 Model Context Protocol and keeps the earlier handshake at the same URL, so existing configs keep working. Clients that only start local servers run npx -y @roxyapi/mcp, which relays the same tools on the same key.
Platform
Name numerology in every major script, name by name
Name numerology reads Cyrillic, Greek, Arabic, Hebrew, Indic, Hangul, kana and Chinese names, Cyrillic and Greek romanized as passports write them (ICAO, ELOT 743), and reduces each name before the total in both systems, every step shown. The Main Challenge spans the whole life.
Platform
Positions read straight from the NASA JPL DE440 ephemeris
Every planet, the Moon, its nodes, Chiron and the four major asteroids now read directly from the NASA JPL DE440 ephemeris, verified against JPL Horizons, the US Naval Observatory and the NASA eclipse canon. Dates run 1550 to 2650, a date outside answers a clear 400, and every monthly table, ingress list, solar return and moon-phase calendar takes any year inside that span.
Platform
Every example is the live engine answering
Every example on the home, product and API pages is the running engine answering the spec request it shows, computed at each release rather than written by hand, and the changelog is also a feed.
Integration
Official n8n node
Install @roxyapi/n8n-nodes-roxyapi in n8n and every domain becomes a Resource and an Operation, with your key entered once for every workflow. Run it as a workflow step or hand it to the n8n AI Agent as a tool, or import the open source astrology AI agent template and chat with it.
Integration
Build on Supabase, in a function or in SQL
A guide and an open source template for Supabase projects. Call any reading from an Edge Function with the typed SDK and no build step, or read endpoints as Postgres tables, and keep what you cache in your own schema under row level security.
UI
Widgets that read like your own site
Every copy-paste widget and hosted embed renders under your brand alone, with a RoxyAPI credit line only where you switch it on. Forms ask visitors for a city wherever a time zone is needed and speak in plain words, in the language of the page.
Platform
South Indian matchmaking on the Vedic API
Two matrimonial endpoints beside Gun Milan: the ten porutham Dashakoot sheet with Rajju and Vedha as hard vetoes, and Papasamyam, the malefic load of both charts from the Lagna, the Moon and Venus. Explained in every supported language.
Platform
Every error links to its own explanation
Every error response now carries a doc_url beside the stable code, pointing at that exact code on the new error reference in the docs. One entry per code, what it means and what to change, so a failing call explains itself in the log.
AI & MCP
Typed results on every Remote MCP tool
Each tool on every domain server publishes an output schema beside its input schema, and a call returns the matching structured result alongside the text, so an agent knows the response shape before it calls and a client can validate what comes back.
New domain
Mesoamerican astrology, Vastu, Kabbalah and Ayurveda
Four new domains on the same key: Maya Tzolkin and Long Count charts with Aztec day signs, Vastu plot, entrance, room and griha pravesh timing, Kabbalah gematria with name and birth profiles, and Ayurveda constitution, dinacharya and ritucharya. Interpretations in every supported language, free calculators on the tools pages.
Platform
Monthly horoscopes gain key dates and a week by week view
Every sun sign horoscope section is written at column length from the real transits of its period, in every supported language. The monthly reading adds keyDates and a weekByWeek breakdown ranked on the same events, so a page shows the month at a glance and drills into any week.
Hi, I am Rosie, your guide to the RoxyAPI insight tools.
Ask me to read your birth chart, pull a card, or map your numbers, and I will 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.