18+ domains. One price.

Plans use request quotas with no credit weighting or premium endpoint surcharges. A natal chart, a tarot draw and a Remote MCP calculation each consume one quota unit. Estimate your allowance from the calculation calls your application makes.

The published Data Processing Addendum is included on every plan. It describes processor obligations, security measures, subprocessors and applicable transfer safeguards. Service data is stored at rest in Germany; review policy/dpa and its annexes for the processing scope and response-cache details.

One subscription covers all 18+ domains and every endpoint. Use a secret key for REST and Remote MCP, or a publishable key for permitted browser integrations. There are no separate product subscriptions or per-domain fees.

Every plan includes Remote MCP access and the complete API catalog. SDKs for TypeScript, Python, PHP, C#, Go, and Rust, MIT-licensed UI components and templates, embeddable widgets and a WordPress plugin provide ways to build on it. Responses support 10+ languages, with localization coverage documented by domain and field.

Remote MCP is included on every plan. Each domain provides a Streamable HTTP server for compatible clients that support the required authentication. Calculation tool calls consume the same request allowance as REST; connection guidance is at docs/mcp.

Use your own model and pay its provider separately for inference. RoxyAPI charges for calculation requests, with Remote MCP and SDKs supplying the data and tools your application calls. API request bodies are never persisted. Responses derived from submitted data may be cached for up to 24 hours; Cache-Control: no-store bypasses the cache. Usage metadata retention is in policy/privacy. Your application keeps user profiles and memory.

For the Sun, Moon, planets and Chiron, RoxyAPI returned 231 of 231 positions within 0.32 arcseconds (0.00009 degrees) of NASA JPL Horizons, at a median deviation of 0.05 arcseconds (0.00001 degrees). The open RoxyAPI benchmark checks 17 domains, each against its own named authority, from planets, angles and sidereal charts to calendars, time zones and printed rules, and returned 2,701 of 2,701 values within their stated tolerance; only tarot, crystals, dreams and angel numbers, which have no outside value to measure, are left out. The methodology page documents the verification suite, including 3,683 gold-standard tests; review methodology, the live report at roxyapi.github.io/astrology-api-benchmark and live output in api-reference.

The API license permits commercial applications without requiring disclosure of your application source. Usage is covered by the subscription allowance, with no per-user royalties or revenue share charged by RoxyAPI. Review policy/license for permitted use and the applicable terms.

Starter includes Western natal charts, horoscopes, synastry and transits, plus advanced techniques such as progressions and astrocartography. Vedic charts, KP, dasha and matching methods are also included, alongside every other RoxyAPI domain. Compare the endpoints, verification evidence and request allowance with your requirements before subscribing.

Compare the request allowance, the calls needed for your feature and the domains included in the subscription. RoxyAPI includes all 18+ domains, Remote MCP and integration tools, with one quota unit per billable calculation request. Published verification evidence and the commercial license are additional checks to make alongside the price.

A hosted subscription supplies maintained calculations, verification evidence and API access across 18+ domains. It also includes Remote MCP and integration paths through SDKs, supported UI renderers and templates. Compare that scope with the ongoing calculation, localization and operational work your own implementation would require.

Choose monthly or annual billing at checkout. API access is activated after payment, and the request allowance follows a UTC calendar month independently of the billing cycle. You can inspect live output in the API reference before paying.

The request allowance resets at the start of each UTC calendar month, independently of your subscription renewal date. Annual plans receive a new allowance each calendar month, and unused requests do not roll over. The account dashboard shows the current allowance and reset date.

Requests that exceed an enforced monthly or per-minute allowance receive HTTP 429. Starter permits 600 requests per minute, with the other plan limits shown at pricing. RoxyAPI does not add automatic overage charges; you can upgrade when you need a larger allowance.

The account dashboard shows your request allowance, consumption and usage by domain, including REST and MCP activity. It also provides endpoint summaries and a request log. Usage warning emails help you monitor consumption as it approaches the monthly allowance.

You can change your plan or billing cycle from the account dashboard or checkout and keep the same API keys. The new allowance applies after payment. Unused paid value is converted into additional time on the new plan, as shown in the checkout quote.

API localization supports 10+ languages: English, Turkish, German, Spanish, Hindi, Portuguese, French, Russian, Chinese (Simplified), Chinese (Traditional). Coverage varies by domain and response field, and untranslated content can remain in English. Check the endpoint language options and its live output in api-reference for the reading you need.

Invoices are issued for payments, including renewals. Directly billed purchases have downloadable invoices in the account dashboard, and billing details can be updated there. If your checkout uses a merchant of record, that seller provides the invoice under its billing terms.