The API path is built for buyers: choose the plan, create the workspace, issue keys, then scale from real usage.
1
Choose the lane
Start with Core Compute when the product needs high-volume astrology infrastructure. Add AI Intelligence only for paid, display-ready moments.
Compare plans and endpoint access
2
Create the workspace
Sign in, create or select the company workspace, and attach the subscription to the account that will own keys and usage.
Open workspace checkout
3
Issue scoped keys
Generate API keys for the selected product surface, keep endpoints scoped by plan, and use idempotency keys for retry-safe billing.
Create a production key
4
Scale from evidence
Review live usage, response quality, support needs, and upgrade timing before moving a partner into production volume.
Review usage and readiness
Live
Live foundation
The public API, checkout route, customer console, usage dashboard, API Lab, and no-AI core routes are in place.
Self-serve checkout and plan discovery
Live
Full Erlewine StarTypes layer
The helio tropical StarTypes endpoint now uses the full packaged Michael Erlewine short ephemeris lookup instead of the old pilot slice.
Scoped API keys after payment
Beta gate
Self-serve beta hardening
The next commercial gate is making a buyer able to discover plans, check out, create keys, run examples, and see usage without hand-holding.
Credit visibility before scale-up
Next build
Endpoint expansion
The strongest roadmap is deeper business functions around dating apps, creator funnels, media intelligence, world signals, and premium spiritual products.
Endpoint examples by use case
Enterprise
Enterprise platform
Large partners need private contracts, committed usage, custom endpoints, stronger observability, and optional realtime or callback products.
Enterprise contracts for private integrations