Build commercially. No AGPL. No copyleft. No strings.
License clarity for builders, founders, and AI agent developers. If you build on RoxyAPI, your product code stays yours.
What you can build and ship
Your subscription grants you a usage license for all API calls within your plan quota. There are no copyleft clauses, no royalty obligations, and no source disclosure requirements attached to that usage.
Build and sell commercial SaaS
Ship subscription products, one-time purchase tools, or pay-per-report services. Monetize however your market demands.
Keep your source code closed
Your application code, business logic, and product remain fully closed source. No AGPL copyleft. No disclosure obligation.
White-label computed responses
Present computed output inside your own branded product. You own the user experience built on top.
Use any LLM provider on top
Combine RoxyAPI data with OpenAI, Anthropic, Google Gemini, or any other AI provider. No lock-in at the infrastructure layer.
Distribute apps in any store
Ship iOS and Android apps via the App Store and Google Play. Nothing in the RoxyAPI license conflicts with mobile distribution agreements.
Run on any cloud or runtime
Deploy on AWS, Vercel, Cloudflare Workers, Hetzner, Railway, Fly.io, or any other infrastructure. No vendor restrictions.
What you cannot do
These restrictions protect the sustainability of the service and the reliability every paying customer depends on.
- Redistribute responses as a standalone dataset. You may not package API responses into a bulk data product, sell them as raw datasets, or re-expose them through a competing API service.
- Resell unmodified API quota. You may not resell, sublicense, or share access to your API key or plan quota with third parties who are not using your own product.
- Claim Roxy Ephemeris as your own engine. Roxy Ephemeris is proprietary infrastructure. You may not represent it as a system you built, license, or operate.
- Use the API after subscription cancellation. API access is active only during a valid subscription period. Calls after expiration are rejected.
- Reverse engineer the underlying calculations. You may not attempt to extract, replicate, or reverse engineer the Roxy Ephemeris computation engine from API responses.
Two things with two licenses. Know which is which.
Developers sometimes conflate the proprietary calculation engine with the open accuracy benchmark. They are separate, with separate terms.
Roxy Ephemeris
Proprietary hosted infrastructure
- Operated by RoxyAPI under standard commercial terms
- Your API key grants usage rights, not source rights. No access to engine code.
- No AGPL restrictions. No copyleft. No source disclosure on your application.
- Verified against NASA JPL Horizons DE441. Sub-arcminute accuracy.
astrology-api-benchmark
Open MIT-licensed accuracy benchmark
- Separate public repo at github.com/RoxyAPI/astrology-api-benchmark
- MIT licensed. Clone, modify, and redistribute freely.
- 210 reference planet positions from NASA JPL Horizons across 21 charts. Run it against any astrology API.
- Runnable Python code included. Extend it with your own charts and reference points.
Reference data sourcing
RoxyAPI uses authoritative external sources to verify calculation accuracy, not as content suppliers. Customers receive computed responses, not third-party data dumps.
Planet positions are verified against NASA JPL Horizons DE441, the authoritative reference for geocentric ecliptic positions. Vedic calculations are cross-referenced against DrikPanchang. KP astrology results are cross-referenced against onlinejyotish.com. Moon phases are verified against timeanddate.com.
These sources are used for testing and calibration only. Every API response is a fresh computation by Roxy Ephemeris, not a query or proxy to any of these sites. No third-party content is redistributed to callers. The verification methodology is published at roxyapi.com/methodology.
Some spiritual data APIs carry license obligations. RoxyAPI does not.
This section is buyer education, not competitive commentary. Understanding why AGPL matters is part of evaluating any API for production use.
The Swiss Ephemeris license problem
Swiss Ephemeris is the most widely adopted ephemeris library in the astrology software industry. It is powerful and accurate. It is also dual-licensed: open source under AGPL, or a commercial license purchased separately. The AGPL clause is what matters for SaaS builders.
AGPL (GNU Affero General Public License) requires that if you run a network-facing service that incorporates AGPL-licensed code, you must publish the complete source code of that service to any user who interacts with it. For a SaaS company, that means your entire application stack. If you do not want to open-source your product, you must purchase a commercial license from the Swiss Ephemeris vendor.
Single-domain Vedic and Western astrology APIs that call Swiss Ephemeris from their server carry this obligation. The obligation is theirs to manage, not yours as a customer. But it is worth knowing that the calculation infrastructure underneath some APIs has this license footprint.
RoxyAPI does not use Swiss Ephemeris. Full stop.
Roxy Ephemeris is a completely independent implementation. It carries no AGPL obligation, no copyleft, and no commercial licensing requirement. Customers calling the RoxyAPI API receive computed responses from a proprietary engine under standard commercial SaaS terms. Your application code stays yours.
The practical implication for your product
Build your astrology app, tarot platform, numerology tool, or AI agent on RoxyAPI. Keep your codebase closed. Ship under any license you choose. Sell subscriptions. Raise funding. No license audit surprises.
License FAQ
Can I build a commercial product on RoxyAPI?
Yes. RoxyAPI is designed for commercial use. Build and sell SaaS products, subscription services, dating apps, wellness platforms, AI chatbots, or any other commercial application on top of RoxyAPI without restriction. Your subscription grants you a usage license for all requests within your plan quota.
Do I have to open source my application?
No. RoxyAPI does not use Swiss Ephemeris or any other AGPL-licensed library. Roxy Ephemeris is proprietary infrastructure operated by RoxyAPI. Calling our API does not create any copyleft obligation on your codebase. Your application code, business logic, and product can remain fully closed source.
Can I redistribute API responses?
No. API responses are computed results delivered for use in your application. You may display and incorporate them in products you build, but you may not package and resell RoxyAPI responses as a standalone dataset, redistribute them as a bulk data product, or re-expose them as a competing API. White-labeling computed output within your own product is permitted.
Is Roxy Ephemeris open source?
No. Roxy Ephemeris is proprietary calculation infrastructure operated by RoxyAPI. Your subscription gives you usage rights through the API, not access to source code. The separately maintained astrology-api-benchmark repository at github.com/RoxyAPI/astrology-api-benchmark is MIT licensed and can be freely cloned, modified, and redistributed. These are two distinct things.
What happens to my data if I cancel?
Your API access is deactivated at the end of your current billing period. After that date, API calls will be rejected. We retain account and billing records for legal and financial compliance. API usage logs are retained for 90 days. You may request full account deletion by contacting us.
One key. Ten domains. Your code stays yours.
No AGPL. No copyleft. No source disclosure. Flat monthly pricing across every spiritual data domain.