Endpoint Access by Plan
A complete reference of which API endpoints are available on each product tier, along with rate limits and monthly unit allowances.
Choosing a Plan
Visit the Billing page to view current pricing and subscribe.
Endpoint Matrix
| Endpoint | advanced_chart | sage_api |
|---|---|---|
Chart (/api/chart) | ✓ | -- |
Composite (/api/composite) | ✓ | -- |
Astrology (/api/astrology) | ✓ | -- |
Transit Chart (/api/transits/chart) | ✓ | -- |
Transit Periods (/api/transits/periods) | ✓ | -- |
All Planets (/api/transits/all) | ✓ | -- |
Moon Range (/api/transits/moon) | ✓ | -- |
Retrogrades (/api/retrogrades) | ✓ | -- |
Returns (/api/returns) | ✓ | -- |
Multi-Chart (/api/multi-chart) | ✓ | -- |
SAGE Query (/api/sage) | -- | ✓ |
| MCP Server | -- | ✓ |
Monthly Unit Limits
Units are consumed per successful API call (1 unit per chart, 1 unit per SAGE query). Multi-chart batch requests consume 1 unit per successful chart in the batch.
| Plan | Billing Cycle | Monthly Units |
|---|---|---|
| Monthly (Whop) | Monthly recurring | 100,000 |
| 3-Month (Whop) | Quarterly recurring | 150,000 |
| Annual (Whop) | Yearly recurring | 300,000 |
| Lifetime (Nas.io) | One-time purchase | 150,000 |
Unit Resets
Unit counters reset on the first day of each calendar month at 00:00 UTC, regardless of your subscription start date.
Rate Limits
Rate limits are enforced per API key on a rolling 60-second window.
| Tier | Requests per Minute |
|---|---|
basic_chart | 60 rpm |
advanced_chart | 120 rpm |
sage_api | 100 rpm |
When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait. See the Rate Limits page for detailed handling guidance.
Quick Reference
advanced_chart-- All chart endpoints: Chart, Composite, Astrology, all Transits, Returns, and Multi-Chart. 120 rpm.sage_api-- SAGE knowledge query and MCP server access. 100 rpm.
Multiple Keys
You can hold API keys on different tiers simultaneously. For example, an advanced_chart key for chart generation and a separate sage_api key for knowledge queries. Each key's rate limit and unit consumption are tracked independently.