White Label Astrology App: What the License Must Allow
White label astrology app checklist: nine license terms that decide whether you can rebrand, keep, rewrite and sell readings, checked against RoxyAPI.
TL;DR
- A white label astrology app needs a data license that permits showing results under your own brand with no vendor mark, keeping them after cancellation, rewriting the text, and building the same app for clients.
- RoxyAPI results carry no vendor mark, need no consent or notice to show your users on any plan, and stay licensed to you perpetually once retrieved during a paid term (Terms 2.6 and 5.2).
- Agencies may build and run client apps on their own key, held in systems the agency operates; a client calling the API directly needs its own subscription.
- Off limits everywhere: reselling API access, republishing responses as a dataset or competing API, and presenting the calculation engine as your own.
RoxyAPI is the data layer for insight, belief and prediction products, and a white label astrology app built on it puts birth charts, daily horoscopes, compatibility and tarot readings in front of users under your brand instead of the data provider. Searches for white label astrology software usually land on turnkey storefronts that host the site, run checkout and sell fixed reports. That is one model. The other is a data API under your own interface, where you own the product, the customers and the margin.
Either way, the storefront is the easy part to replace. The license decides whether the brand on the screen is really yours: whether a vendor mark must stay, whether saved charts survive a cancelled subscription, whether you may rewrite the readings in your own voice, and whether an agency may build the same app for several clients. This guide sets out those terms as checks you can run on any provider, with the clause behind each RoxyAPI answer.
What does white label mean for an astrology app?
White label means your users see your brand, your design and your voice, while the computation and the editorial content come from a provider they never see. For an astrology app there are three ways to get there, and they differ on who owns the customer.
| Model | Who owns the interface | Who owns the customer relationship | The question that decides it |
|---|---|---|---|
| Hosted storefront | Provider, skinned with your logo | Provider runs checkout and delivery | Can you take your customers and their saved readings with you? |
| Report resale | Provider writes and formats the report | Shared, per sale | May you edit the text, and does the provider mark stay on it? |
| Data API under your UI | You | You | Does the license let you show, store and rewrite results indefinitely? |
The third model is the one a developer, agency or media company builds on, because every screen, price and email stays under their control. It is also the one where the license carries the whole weight, so it gets the checklist.
Which license terms decide whether a white label app is safe?
Nine terms decide it, and every one is answerable from published documents before you write a line of code. Run them on each provider on your shortlist.
| # | Check | RoxyAPI answer | Source |
|---|---|---|---|
| 1 | Must a vendor mark appear on the result? | No. Nothing in a response has to be shown as a credit, and widgets render under your brand alone; a credit line appears only if you switch it on | License, widgets |
| 2 | Do you need consent to show results to your users? | No consent and no notice, on any plan, in any country, including when readings are most of what your users get | Terms 2.6 |
| 3 | Do saved results survive cancellation? | Yes. The license to every result retrieved during a paid term is perpetual and irrevocable | Terms 5.2 |
| 4 | May you store and cache responses? | Yes, in your own systems, for as long as you need them | Terms 5.1 |
| 5 | May you rewrite or translate the interpretation text? | Yes, into your own voice and into languages the API does not ship; altered text is not presented as RoxyAPI editorial content | Terms 5.3, License |
| 6 | Are your derived works yours? | Yes. Translations, rewrites and summaries are your works, and you may keep producing outputs from them after cancelling | Terms 5.4 |
| 7 | May you run results through an LLM? | Yes, at inference time with any provider, no consent needed. Training a model on responses is consent-gated | Terms 2.5 |
| 8 | Does the engine put copyleft duties on your code? | No. Roxy Ephemeris is proprietary and hosted, and no AGPL code runs in the service | License |
| 9 | Where does the birth data of your users go? | Data submitted to the API is stored in Germany, request payloads are never written to disk, and the published DPA applies on every plan | Data protection |
Checks 3 and 5 are the ones most often missed. A license that ends with the subscription turns a vendor change into an outage for every user with a saved chart. A license that forbids editing the text means the white label reading still sounds like another company. The full set of exit terms is covered in the vendor diligence guide.
Building a white label product on these terms? The Astrology API and every other domain run on one key, and pricing is flat per request.
Can an agency build white label astrology apps for its clients?
Yes. Terms section 2.6 lets an agency or studio build and operate products for its own clients on the same basis as its own products, provided the API key stays in systems the agency operates. One subscription can power several client apps, with separate keys that can each be rotated or revoked, and the Business plan is built for platforms and agencies.
The line is between delivering an experience and handing out access. The users of a client app may receive charts, readings and interpretations in any form the app presents them. A client that wants to send its own requests to the API needs its own subscription, and a pass-through endpoint that lets others query through your key needs consent. Two patterns keep agency builds clean:
- Server side: a secret key stays in the backend you run, and the client app calls your backend.
- Browser side: widgets and components run on a publishable key, made to sit in page source and lockable to the client domain.
How do you put your own brand on the front end?
Three surfaces cover most builds, and none of them requires a RoxyAPI mark.
- Templates. Open source apps under the MIT license: an AI chatbot, a companion with memory, a practitioner website, Vedic and tarot apps. Clone one, change the name, colors and copy, and ship it as your own. The catalog is at /templates.
- UI components. Web components for natal wheels, kundli charts, horoscope cards and tarot spreads. Every component reads
--roxy-*CSS custom properties, so 30+ tokens for color, spacing, radius and motion match your brand without a rebuild. See UI components. - Widgets. Copy-paste readings for sites with no backend, including WordPress, Shopify, Wix and Squarespace, powered by a publishable key. The credit line is off by default.
How does one key serve every language and domain you sell?
One key covers all 18+ domains, from Western and Vedic astrology to human design, numerology and tarot, and translated endpoints take a lang query parameter. A white label product for a Spanish-language audience asks for Spanish and gets reader-facing text in Spanish, while machine values such as the sign name stay canonical for your code to switch on.
curl -s "https://roxyapi.com/api/v2/astrology/horoscope/leo/daily?date=2026-10-23&lang=es" \
-H "X-API-Key: YOUR_KEY"{
"sign": "Leo",
"date": "2026-10-23",
"overview": "El Sol entra en Escorpio hoy, y el asunto se juega en tu cuarta casa reservada a hogar y bases emocionales...",
"events": [
{ "type": "aspect", "at": "2026-10-23T04:40:29Z", "bodies": ["Mercury", "Jupiter"], "aspect": "square", "house": 4, "through": "2026-10-31T10:43:18Z" }
],
"luckyColor": "Naranja",
"moonSign": "Piscis",
"compatibleSigns": ["Aries", "Sagitario", "Géminis"]
}The events array dates every transit the column is written from, so an editor on your side can check each line before it ships under your masthead. The same key returns a natal chart, a tarot daily card or a numerology profile, so a publisher adding a second domain adds an endpoint, not a vendor.
FAQ
Can I sell a white label astrology app under my own brand?
Yes. RoxyAPI results may be shown to the users of any product you build, including a paid consumer app or subscription service, with no consent and no notice on any plan (Terms 2.6). Nothing in a response has to be shown as a credit. The limits are reselling API access itself and presenting the calculation engine as your own.
Do I have to show "Powered by RoxyAPI" in my app?
No. API responses need no on-screen credit, and widgets render under your brand alone. A small "Spiritual data by RoxyAPI" credit appears only if you switch the attribution option on.
Can I resell RoxyAPI access to my clients?
No. You may build and run apps for clients on your own key, held in systems you operate, but you may not resell, sublicense or share your key or plan quota (Terms 5.5). A client that wants to call the API directly takes its own subscription.
What happens to saved charts if I cancel?
They stay yours. The license to every result retrieved during a paid term is perpetual and irrevocable and survives cancellation (Terms 5.2). Cancelling stops new API calls only, so stored charts and readings keep serving your users.
Can I translate horoscopes into a language the API does not ship?
Yes. Terms 5.3 lets you translate, edit and rewrite interpretation text to fit your product, including into languages the API does not offer. Your translations are your works under Terms 5.4, and you may keep serving them after you cancel.
Does a white label app built on RoxyAPI have AGPL obligations?
No. RoxyAPI runs its own proprietary engine, Roxy Ephemeris, and no AGPL-licensed code runs in the service, so calling the API creates no copyleft obligation on your codebase. Your app can stay closed source.
Conclusion
A white label astrology app is defined by its license, not its storefront. Check that results carry no required mark, survive cancellation, may be rewritten in your voice and may power client builds, then pick the front end that fits: a template, UI components or widgets. Read the license policy in full and start with the Astrology API.
