Question 1

Do all requests cost the same?

Accepted Answer

Yes. Every API request consumes exactly one token, regardless of which endpoint you call. A birth chart calculation costs the same as a tarot draw or a dream lookup. No surprise pricing tiers, no per-endpoint surcharges. Remote MCP is billed identically: one MCP tool call counts as one request, and tool discovery (an agent listing the available tools) is always free. Flat, predictable pricing.

Question 2

Are there hidden credit costs or premium-endpoint surcharges?

Accepted Answer

No. One request equals one quota unit, with no credit weighting and no premium multipliers. A full birth chart, a complete panchang, or a detailed report each cost a single request. Credit-metered providers work differently, and the spread is far wider than the headline price suggests. On one published credit table (checked June 2026) a basic panchang call draws 10 credits, a birth chart 50, a daily horoscope 250, and a single regional-calendar call 2,000. That is a 200x swing between two calls on the same wallet, and individual report modules run from 200 up to 75,000 credits each. Your bill then depends on which endpoints your users happen to hit rather than on how many people used your app, which is impossible to forecast before you ship. RoxyAPI stays flat, so cost tracks real usage and never surprises you.

Question 3

Can I use the same API key to access all APIs?

Accepted Answer

Yes! One API key gives you access to all 12 RoxyAPI domains. Unlike competitors who charge per product, we believe in simple, unified access. Your subscription covers everything - no per-product fees or separate keys needed.

Question 4

What comes with a plan besides API requests?

Accepted Answer

One flat subscription unlocks the whole build surface at no extra cost: typed SDKs for TypeScript, Python, PHP, C#, and Go, drop-in @roxyapi/ui components that render charts and readings straight from the response, copy-paste embeddable widgets for Squarespace, Wix, Shopify, Ghost, Webflow, or any site with an HTML block, plus a hosted embed URL for platforms like Notion and Stan Store that cannot run a script, MIT-licensed starter templates, a WordPress plugin, a Remote MCP server for every domain, llms.txt and AGENTS.md so AI coding agents wire it up on their own, Postman collections, and localized responses in 8+ languages. Competitors meter these as add-ons or skip them entirely; here every domain and every tool is included under one key.

Question 5

Is Remote MCP included, or does it cost extra?

Accepted Answer

Included on every plan at no extra cost. Each of the 12 domains ships a Remote MCP server over Streamable HTTP that Claude Desktop, Cursor, VS Code, ChatGPT, and other agents connect to and start using in seconds. Nothing to self-host, no local process, no Docker. Remote MCP is part of the core architecture, not a bolted-on wrapper.

Question 6

Do you charge per token for AI, or can I bring my own model?

Accepted Answer

Bring your own model. RoxyAPI returns structured, verified data that your own agent grounds its answers on, so there are no per-query or per-token AI fees and no hidden system prompt between you and the result. RoxyAPI is also stateless: we store no end-user data, no birth details, journals, or profiles, so no personal data ever leaves your stack and you own the memory and personalization layer with no third-party processor liability. Your users get answers in your voice, inside your product, not a vendor-branded chatbot with markup. To start from a working example, clone one of our MIT licensed starter template from our free templates page: the open-source AI astrology chatbots already ship the guardrails and call Roxy Remote MCP tools for every calculation, so you plug in your own model and go.

Question 7

How accurate are the calculations, and how is that verified?

Accepted Answer

Every calculation comes from Roxy Ephemeris, and 6,044 automated tests run on every deploy. 1241 of those are gold-standard tests locked to named external references, with NASA JPL Horizons DE441 as the primary reference for planetary positions and an authoritative source named per domain for everything built on top, backed by a public MIT-licensed benchmark anyone can re-run. The check is against physics ground truth, not a self-referential comparison to another astrology library, so a raw test count with no external oracle behind it is not the same claim. You can audit it before you pay: the live playground at /api-reference returns real production responses, not fake sandbox data, with no signup. The methodology page shows the full verification matrix.

Question 8

Can I build a commercial, closed-source app and sell it?

Accepted Answer

Yes, on every plan. Your subscription is a commercial usage license for all API calls within your quota, with no copyleft, no royalties, and no source-disclosure requirement. Build and sell subscription SaaS, one-time tools, or pay-per-report products, keep your application code fully closed, combine RoxyAPI with any LLM, and ship to the App Store and Google Play. There is no AGPL exposure, because Roxy Ephemeris is proprietary hosted infrastructure rather than a Swiss Ephemeris wrapper, so the copyleft that reaches network services never touches your product. The MIT-licensed starter templates and accuracy benchmark are separate open artifacts you can fork and rebrand. Full terms are on the license page at /policy/license.

Question 9

Why not use a cheaper or free astrology API?

Accepted Answer

Compare the unit, not the sticker. One subscription covers all 12 domains, which is $2.70 per domain per month on annual billing, where a single-domain API typically starts at $12 and covers one tradition. Then look at what the cheap number hides. Credit-metered providers split one result across several billed endpoints, so a complete natal chart can draw four or five charges while RoxyAPI returns it in one request at one quota unit. And a free or near-free engine is usually built over Swiss Ephemeris, which is dual licensed as a paid commercial license or the AGPL, whose copyleft is triggered by network access rather than distribution. Google bans AGPL code company-wide for that reason, stating the risks heavily outweigh the benefits. An astrology API is a network service, so that exposure can reach the product you build on top. Honest exception: if you need exactly one domain, you can run the infrastructure yourself, and you are comfortable with the licensing, a self-hosted library is cheaper and we will not pretend otherwise. For anything multi-domain, agent-facing, or commercial, RoxyAPI is the lower total cost.

Question 10

Why pay when I could build this myself?

Accepted Answer

You can, and the raw math is a few days of work. The catch is licensing: the common open-source ephemeris libraries are AGPL, which forces any network service to either open-source its entire codebase or buy a commercial license. Google bans AGPL code company-wide for exactly this reason. RoxyAPI runs Roxy Ephemeris with no AGPL obligations, verified accuracy with edge cases covered, 12 domains under one key, Remote MCP, and typed SDKs that each take months to reach. You proxy through one clean API instead of inheriting a copyleft liability.

Question 11

How does billing work?

Accepted Answer

Choose monthly or yearly billing. Your API key is generated instantly after payment. Monthly request quotas reset on the 1st of each month (UTC). No credit card required for testing.

Question 12

What happens if I exceed my limits?

Accepted Answer

Requests are rate-limited at the threshold of your plan. You can upgrade anytime to increase your limits.

Question 13

Can I change plans?

Accepted Answer

Automated plan switching is not yet supported. To move to a different tier, cancel your current subscription and subscribe to the new one. Your access continues through the end of the current billing period. We recommend estimating your monthly request volume before subscribing so you start on the right plan.

Question 14

Do you support multiple languages?

Accepted Answer

Yes. API responses are available in 8+ languages: English, Turkish, German, Spanish, Hindi, Portuguese, French, Russian. Add ?lang=es to any endpoint to get localized responses across all translated packages.

Question 15

Do you provide invoices for payments?

Accepted Answer

Yes. An invoice is issued for every payment, including renewals, and is available for download from the account dashboard. Payments in USD or EUR receive a commercial invoice suitable for accounting and expense reporting. Payments in INR receive a GST-compliant tax invoice under GST law; registered businesses can add their GSTIN in the account dashboard to claim input tax credit on the GST charged. Purchases completed through Dodo Payments are invoiced by Dodo Payments as the merchant of record.

Capability	RoxyAPI	Legacy astrology APIs	DIY open source libraries
Platform
Count domains as distinct systems, not as features of one. Horoscopes, natal charts, synastry and compatibility are all astrology and count once here, so an honest total can read smaller than a padded one, and a high endpoint count usually means one result split across separately billed calls.
One key, 12 domains Astrology, vedic astrology, forecast, human design, numerology, tarot, and more behind a single subscription and a single API key.	Yes	Per product	One library each
Flat request pricing 1 request equals 1 unit, REST or MCP, with no credit weighting and no premium endpoint surcharges.	Yes	Credit tables	Self hosted
One call, complete result A natal chart or kundli returns whole in one response instead of splitting into many separately billed calls.	Yes	Split calls	Assembly required
New domains at no extra cost Every new domain lands inside the existing plan automatically.	Yes	New invoice	New build
Simple surface, advanced core
One request returns a complete result, so the advanced layer lives inside the engine instead of inside your integration. RoxyAPI is built by a small, independent team of senior engineers, each with over 20 years building consumer and lifestyle products at scale, including at some of the biggest names in the industry.
Western astrology past the natal chart Fixed stars, asteroid goddesses, Arabic lots, Black Moon Lilith, aspect pattern detection, secondary progressions, solar arc directions, annual profections, astrocartography, relocation charts, local space, and the solar, lunar and planetary return charts.	Advanced layer	Natal and transits	Raw positions
Classical Vedic with the reasoning attached A yoga verdict carries the classical evidence that triggered it and the precedence rule that silenced it, so an agent can explain a judgement instead of restating a label. Shadbala, bhava bala, ashtakavarga, Arudha padas, Chara Karakas, three avastha systems, and KP sub-lords ship alongside it.	44 verdicts, with evidence	Yoga names	Positions only
Human Design past type and authority Variables with Color, Tone and Base, the advanced Primary Health System layer, plus Penta for small groups, two-person connection charts, and transit overlays on a natal bodygraph.	Variables and Penta	Type and profile	No engine to fork
Domains that compose, not just coexist Human Design is computed FROM the western ephemeris and the I Ching hexagrams rather than bolted on as a separate product line, so every gate activation carries its hexagram, and one forecast request merges western transit events with Vimshottari dasha boundaries and biorhythm critical days into a single time ordered feed. The sidereal and tropical engines are tested to return the same sky at zero tolerance.	One shared engine	Separate products	You merge it
Licensing and privacy
The AGPL exposure most teams carry was never a decision: a package manager hands you the free path, so a team installs a Swiss Ephemeris wrapper, ships a network service, and inherits copyleft without reading it. That licence is a private contract with no public registry, so ask any provider for their position in writing.
Own engine, not a Swiss Ephemeris wrapper Roxy Ephemeris is built in house and verified at NASA JPL Horizons parity. Legacy engines wrap Swiss Ephemeris, a 1990s AGPL copyleft library written for single-user desktop software.	Roxy Ephemeris	Swiss based (AGPL copyleft)	Swiss based (AGPL copyleft)
No AGPL exposure The AGPL on Swiss Ephemeris reaches network services, so products built on unlicensed wrappers inherit the obligation whether they know it or not. Google bans AGPL dependencies outright.	None	Inherited from Swiss	AGPL common
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. No source disclosure.	Yes	Varies	Copyleft terms
Stateless, zero user data stored No birth data, journals, or profiles retained, so there is no store to breach and nothing to export or erase when a data subject request arrives. Birth data that can qualify as GDPR Article 9 special category is computed in memory and never lands in a database.	Yes	Accounts and logs	Self hosted
EU data residency with an Article 28 DPA on every plan Stored data stays in Germany, inside the EU, on every plan and for every customer, so an EU buyer gets EU residency by default instead of paying for a regional tier. The processor contract, EU Standard Contractual Clauses, security measures, dated subprocessor register, and breach notification terms are all published, so procurement can review them without contacting us.	Germany, all plans	Enterprise or on request	Yours to write

12 Domains. One Price.

Starter

Professional

Business

Enterprise