The RoxyAPI Transparency Report

RoxyAPI is independently operated by Roxy Labs. Engine development began in 2020 and the platform has run in production since 2024. This report publishes product scope, verification evidence and dated usage figures for buyer diligence.

RoxyAPI is operated by Roxy Labs. The report links the company and founder profiles so you can verify who stands behind the service. Product history and verification evidence are published alongside those identities.

One subscription covers 18+ insight domains, including advanced Western techniques such as fixed stars, progressions and astrocartography, and Vedic KP, dasha and matching methods. The live API reference documents their inputs and outputs. Remote MCP, SDKs and supported UI renderers provide integration paths alongside that calculation depth.

Check domain and endpoint scope against the OpenAPI specification, and inspect published SDKs, UI components and templates in the public repositories. Test figures describe the verification suite documented in /methodology. Usage figures are measured production aggregates with the period stated beside each metric.

Usage figures carry their own measurement periods, so they may describe different months. Structural figures describe the product surface at the report update. Read the date and scope beside a figure when quoting it.

RoxyAPI does not publish a paying-customer count. Account and visitor figures on this page describe different measures and must not be treated as customer totals. Reviews, live API responses and the benchmark provide separate product evidence.

The report records 800+ active users and integrations in June 2026, and 2K+ regular developer visitors in June 2026. These are distinct account and visitor measures, not a paying-customer count. Customer stories are at /reviews.

Verified customer stories at /reviews name the customer and link their product, each published with the written approval of that customer. There is no logo wall. Use the benchmark and live API reference to evaluate the requirements of your own application.

The platform has run in production since 2024. It crossed 1M+ cumulative API requests in March 2025. Later usage measurements are listed separately with their own periods on this report.

The measured monthly request figure is 4.5M+ for September 2026. The earlier 1M+ cumulative milestone was reached in March 2025. These are dated measurements rather than a live traffic counter.

The report records 1.5M+ calls from AI agents and MCP clients in September 2026. That figure describes the stated measurement period. It does not establish a current growth rate or a count of distinct customers.

A measurement period gives each published usage figure a clear scope. The report presents dated aggregates rather than a live dashboard. Quote the period with the number so an earlier measurement is not read as current traffic.

Published usage figures are rounded down to the stated band. The displayed number is a threshold for the measurement period rather than an exact count. Keep that qualifier when quoting a figure.

The public status page shows measured availability and incident history. The Enterprise uptime target is 99.95%, with applicable service credits described in the terms. An SLA target and a measured availability figure describe different things.

Use the public status page linked in the External Validation section of this report. It shows timestamped incidents and availability monitoring. Review the recorded period when assessing the history relevant to your application.

API response time varies by endpoint, workload, caching and network path. Test representative requests from your deployment region under the concurrency your application expects before setting a latency budget.

Planetary positions are verified against NASA JPL Horizons; derived calculations are checked against the reference named for each domain. The suite contains 13,405 automated tests, including 3,620 gold-standard tests. The public planetary benchmark can be rerun independently.

The MIT-licensed benchmark at github.com/RoxyAPI/astrology-api-benchmark compares planetary positions with NASA JPL Horizons. Follow its documented setup and reference conventions for a reproducible run. Other quantities use the authorities and school conventions listed in /methodology.

The public benchmark reports a median deviation of 0.05 arcseconds (0.00001 degrees) against NASA JPL Horizons. Its README at github.com/RoxyAPI/astrology-api-benchmark documents the run, dataset and comparison conventions. Refer to that source for per-body and per-chart results.

The MIT-licensed benchmark is provider-agnostic. It can compare a provider with NASA JPL Horizons using the documented dataset and coordinate conventions. Keep those settings consistent when comparing run results.

Western astrology includes fixed stars, asteroids, Arabic lots, progressions, solar arc and astrocartography alongside natal charts and horoscopes. Vedic astrology includes KP, dasha, panchang, Shadbala and matching methods. These techniques share the same subscription with the other insight domains, with schemas and live examples in /api-reference.

Assess the endpoints your product needs, their verification evidence and the request allowance required for your workload. RoxyAPI combines 18+ domains under one subscription with Remote MCP, SDKs, supported UI renderers and templates. The live reference, methodology register and commercial license make those checks available before subscribing.

The interactive API reference lets you submit example requests and inspect live responses. Test the inputs, fields and interpretation coverage your application needs. Free calculators provide selected readings, while templates show example applications.

RoxyAPI computes its domain results rather than proxying calls to another astrology API. Astronomical calculations use the in-house Roxy Ephemeris engine. The methodology register names the references used to verify those results.

The commercial API license permits hosted calculation use without requiring disclosure of your application source. RoxyAPI does not charge per-user royalties or take application revenue share. The API terms and the separate MIT licenses for SDKs, UI components and templates are available for review.

RoxyAPI provides a Remote MCP server per domain over Streamable HTTP. Compatible clients need to support that transport and the required authentication. The setup guide at /docs/mcp explains how to connect.

The report lists 258 domain tools across 18 domains. A domain server exposes its own subset, so listing one server does not return the combined catalog. The API reference and MCP documentation describe the corresponding operations.

The versioned OpenAPI contract informs the Remote MCP tool schemas. Breaking changes require a new version prefix, and retiring an endpoint or version carries at least 90 days of notice on every plan. Review the schema and changelog when updating an integration.

The report brings together dated usage figures, product scope and links to verification evidence. Check the scope and measurement period of each fact before using it in a vendor assessment. The API reference, benchmark and published policy documents support further review.

The OpenAPI specification documents API inputs and response schemas. Documentation is also available through llms.txt and the Docs MCP server for coding agents. SDK playbooks provide integration guidance alongside the generated packages.

RoxyAPI provides SDKs for TypeScript, Python, PHP, C#, and Go, Remote MCP and MIT-licensed templates. Roxy UI renders supported chart and reading responses, while widgets and the WordPress plugin provide website integrations. These paths use the same domain catalog and subscription allowance.

Roxy UI supplies themeable components for supported responses, including natal wheels, Vedic charts, panchang tables and tarot spreads. It offers web components plus typed React and Vue packages. Available renderers are listed at /ui, and embeddable widgets are at /widgets.

The official WordPress plugin adds supported readings through shortcodes. The widgets gallery supplies script snippets, iframes and hosted links for sites that permit those formats. Choose a supported widget and configure its publishable key for the host site.

Roxy Ephemeris is proprietary hosted infrastructure. The SDKs, UI components and templates are separate MIT-licensed artifacts. The API license covers commercial access to the hosted calculations.

Revenue and MRR are private business figures and are excluded from this report. The published evidence covers product scope, verification, dated usage and availability. Those measures support product diligence without presenting private financial statements.

The report excludes paying-customer totals, revenue, MRR and raw live dashboards. It publishes selected structural metrics, verification evidence, dated usage measurements and status links. Each published figure carries the scope needed to interpret it.

You can quote the published facts with their measurement period, scope and qualifiers. The Citable Facts block links the supporting evidence for each statement. Cite the relevant proof link so readers can check the source.