AstroWay/api v2.204.2 · fr
tous les systèmes sont opérationnels

Free Astrology API: Which One Has the Best Free Tier in 2026?

A side-by-side of free tiers across the major astrology APIs - credits, request caps, card requirements - and how much you can actually build for free.

“Free astrology API” usually means one of three things: a generous monthly credit grant, a hard daily request cap, or a time-limited trial that turns into a paywall. They are not the same, and the difference decides whether you can ship a side project without a card. Here’s how the main options actually compare.

AstroWay’s free tier is 10,000 credits per month, no credit card. A full natal chart is 20 credits, so that’s roughly 500 charts a month before you pay anything - the most generous standing free tier among the commercial astrology APIs as of 2026.

APIFree allowanceCard required?Notes
AstroWay10,000 credits/mo (~500 natal charts)NoStanding monthly grant across all 761 endpoints
Prokerala~2,500 creditsNoVedic-focused; credit costs vary widely per endpoint
FreeAstrologyAPI~50 requests/dayNoHard daily cap, no SDK
DivineAPI14-day trialYes (usually)Trial, not a standing free tier
VedikaNo live free tier–Paid from the start

Competitor figures are estimates from public pricing pages (June 2026) and change; check each provider before you commit.

”Credits” vs “requests” - read the unit

Section titled “”Credits” vs “requests” - read the unit”

A daily request cap (FreeAstrologyAPI’s ~50/day) is predictable but small, and a single complex call counts the same as a trivial one. Credit grants (AstroWay, Prokerala) price by what the endpoint computes - a planet lookup is cheap, a rectification is not - so a credit tier stretches further for a mix of light calls. The catch with some credit systems (Prokerala’s is the usual example) is that a few heavy endpoints can burn a month’s budget fast, which makes planning hard. AstroWay’s per-endpoint costs are flatter and published on the pricing page.

At 20 credits per natal chart, 10,000 credits is about 500 charts a month. In practice that covers:

  • a personal project or MVP serving real users before any revenue,
  • a daily-horoscope widget caching twelve sign-based calls per day (a few credits each),
  • local development and CI without touching a paid key.

When you outgrow it, the first paid tier starts at $5/mo.

Terminal window
# Python
pip install astroway
// TypeScript
npm install @astroway/sdk

Generate a key on the dashboard - no card - and the free credits are active immediately.

MakSeong · AstroWay

Je fais l'API AstroWay : j'enveloppe Swiss Ephemeris dans du REST pur et j'écris sur les détails ennuyeux qui sont en fait importants.

// construis avec ça

Le même Swiss Ephemeris que Solar Fire - en 4 lignes de code.

Clé gratuite sans carte. 5 000 appels par mois avant le premier paiement.

Plus d'articles du blog voir tous les articles →

Ephemeris 2026-07-19

Comment nous maintenons l'exactitude sous contrôle : CI contre swetest et NASA

L'exactitude dans l'API astro se dégrade facilement d'une refonte des éphémérides. Nous décomposons la protection : un noyau Swiss Ephemeris pour l'application et l'API, des centaines de snapshots gelés sur les cartes de référence et la triangulation de chaque PR contre swetest CGI, Kerykeion, Prokerala et le catalogue d'occultations de NASA.

Engineering 2026-07-15

Trois SDK officiels : TypeScript, Python, PHP au lieu de curl brut

Le HTTP brut fonctionne, mais le client typé économise des heures : autocomplétion des chemins, types de requête et de réponse, retry intégré pour 408/409/429/5xx et hiérarchie de erreurs à la manière de Stainless. Nous démontons les trois SDK officiels - @astroway/sdk (npm), astroway (PyPI), astroway/sdk (Packagist) - et comment ils sont générés à partir d'un même contrat OpenAPI.

Engineering 2026-06-05

Horoscope API Tutorial: Build a Daily Horoscope Feature

Add daily, weekly and monthly horoscopes to your app via API - sign-based text vs transit-based personalization - with TypeScript and Python code.