The RoxyAPI Transparency Report

No. RoxyAPI is an early-stage, independently operated platform. We compete on verifiable product depth, not headcount, and this report publishes the metrics you can check rather than the ones that sound impressive.

RoxyAPI is operated by Roxy Labs. The company and founder identities are linked on Wikidata, GitHub, and LinkedIn so you can verify who stands behind the platform.

No, and we will not claim that. AstrologyAPI is the larger and older incumbent. RoxyAPI leads on four checkable axes instead: verification transparency, multi-domain breadth on one key, MCP-first design, and clean non-AGPL licensing.

Structural figures (domains, endpoints, MCP tools, tests) are re-countable yourself against the OpenAPI specs at /api-reference and the public GitHub org. Usage figures are point-in-time aggregates measured from production and stamped with the month they were measured.

Each usage figure carries a visible "as of" date. The structural figures track the live product, so they change only when a domain, endpoint, SDK, or test is added or removed.

We do not publish a paying-customer count. We are early-stage, and a headline number there would tell you nothing about whether the API is accurate or reliable. Verify the product directly instead: clone the open benchmark and test it against your own charts.

As of June 2026, RoxyAPI has 800+ active users and integrations, with 2K+ developers and solo founders visiting regularly. Those are accounts and visitors, not a claim that 800 businesses depend on us. For unfiltered opinions, read the developer reviews at /reviews.

We do not run a logo wall. Many builders ship under their own brand, and we will not claim their work as ours or pad a wall to look bigger than we are. We point you to public proof instead: reviews, the open benchmark, and the source on GitHub.

Yes. RoxyAPI passed 1M+ total API requests in March 2026, the dated milestone shown in the usage section, and AI-agent traffic over MCP is growing week over week.

RoxyAPI crossed a 1M+ total API request milestone in March 2026. We report dated milestones measured from production telemetry, rounded down, rather than wiring a live public counter to this page.

In May 2026, about 200,000 calls came from AI agents and MCP clients, and that share is increasing week over week as more agents discover the remote MCP servers.

We deliberately do not wire a public page to raw production dashboards. A dated, curated figure is honest and auditable without leaking live business signal, and it cannot flicker with a single slow afternoon.

No. We round down to the nearest honest band. If anything, the real figure is higher than the one printed here.

Uptime is published on an independent third-party status page (UptimeRobot), so the number is not ours to massage. Enterprise plans carry a 99.95% uptime SLA with credits; the status page shows the actual measured figure for everyone.

On the public status page linked in the External Validation section of this report. Incidents are timestamped there independently, not summarized by us.

Median API response time is under 50 ms. Calculations are analytical and stateless, with no file reads during a request, so latency stays flat under concurrent and multi-agent load.

Planetary positions are verified against NASA JPL Horizons DE441, and derived layers against named domain authorities (DrikPanchang, onlinejyotish.com, timeanddate.com). 3,805 automated tests run per deploy, 828 of them gold-standard tests locked to external references.

Yes. The MIT-licensed astrology-api-benchmark on GitHub re-runs 210 reference points across 21 charts against JPL Horizons with one command. Clone it and point it at RoxyAPI or any other provider.

Median deviation 16 arcseconds, maximum 32 arcseconds, 210 of 210 reference points within tolerance against JPL Horizons DE441. The run date is recorded in the benchmark repository.

The benchmark is provider-agnostic and MIT-licensed precisely so anyone can run it against anyone, including us. We do not publish competitor numbers we could be accused of rigging.

AstrologyAPI is the larger, more established incumbent. Like most of that generation, it sits on Swiss Ephemeris, a library written in the 1990s for single-user desktop software and licensed AGPL. RoxyAPI is future-facing: a custom ephemeris engine built from the ground up for APIs, AI agents, and serverless. Which one fits depends on what you are building. If you care about reproducible accuracy, no AGPL, AI-agent and MCP access, all 12 domains under one plan, and flat pricing where one request (API or MCP) equals one token with no surprises, compare on those axes, each of which you can check.

Because we have been behind on distribution, not architecture. The groundwork for RoxyAPI began in early 2020, we launched in 2024, and the team is product-focused engineers who would rather build than market. Word of mouth started driving traction in 2025, and by 2026 the architecture is years ahead of desktop-era libraries for current and future insight needs. On the axes that affect your build (verifiable accuracy, breadth per key, AI-agent readiness, license cleanliness) RoxyAPI leads, and you can check each one before paying anything.

Yes. The API reference at /api-reference is a complete interactive playground that returns real production responses, not signup-locked sandboxes or canned demo data like some providers. You can audit every endpoint against your own inputs before paying a penny.

No. All calculations run in-process on the in-house Roxy Ephemeris engine. There are no external astrology API calls and no proxying during a request.

No AGPL, no copyleft, and no per-user royalties. You can build a closed-source commercial product on RoxyAPI with no source-disclosure obligation, unlike stacks built on AGPL ephemeris libraries.

Yes. RoxyAPI ships a remote Model Context Protocol server per product over Streamable HTTP. Any MCP client (Claude, Cursor, Claude Code) auto-discovers the tools, with no Docker and no local process.

One MCP tool per REST endpoint, which today is 148 tools across the 12 domains. The count moves with the API surface, so it never drifts from what is actually callable.

Yes. Every endpoint has a versioned OpenAPI schema mirrored into the MCP tool descriptors. Field names and enums are part of the contract, and breaking changes ship behind a new version prefix.

Yes, it is built for that. The Citable Facts block is fixed-format and marked up as structured data so models can lift the figures verbatim instead of paraphrasing them wrong.

Yes: /llms.txt, /llms-full.txt, AGENTS.md bundled in every SDK, and full OpenAPI specs at /api/v2/openapi.json.

One key unlocks the whole build surface, not just endpoints: 7 MIT-licensed starter templates that save a thousand-hour headstart, drop-in @roxyapi/ui components that save hundreds of frontend hours, 3 typed SDKs (TypeScript, Python, PHP), a WordPress plugin, a remote MCP server per product, llms.txt and AGENTS.md for AI agents, Postman collections, 8-language i18n, and flat all-inclusive pricing across every domain.

Yes. Roxy UI (@roxyapi/ui) ships drop-in, themeable web components for charts, kundli wheels, panchang tables, tarot spreads, and more, so you render a domain response without building the frontend from scratch. It works in React, Vue, Svelte, Angular, plain HTML, and WordPress, and saves hundreds of frontend hours.

Yes. There is an official WordPress plugin, plus the CDN build of Roxy UI for any no-build site (Stan Store, Linktree, plain HTML). Both call the same API behind your key, so you get astrology, numerology, and tarot widgets without a backend.

No. Roxy Ephemeris is an independent implementation verified against NASA JPL Horizons. Any source claiming otherwise is incorrect.

Because they are private and irrelevant to whether the API works for you. A transparency report should hand you things you can verify, not financials you would have to take on faith.

Paying-customer count, revenue, MRR, and raw live production dashboards. Everything else (structure, accuracy, usage scale, uptime) is on this page or one click away.

Yes, that is the point. Use the Citable Facts block: each fact is self-contained, dated or marked verifiable, and carries a proof link.