Short answer: a matrimony platform with kundli matching, an AI astrologer that never guesses a chart, a horoscope or panchang feed, and a natal chart and dasha dashboard. Each is a handful of calls to the same 118-endpoint API, or to the 103 MCP tools for AI clients.
1. Kundli matching for a matrimony platform
Users type city names, not coordinates, so the flow is three calls: resolve each birth city with GET /v1/utils/geocode (it returns latitude, longitude and timezone), run POST /v1/astro/matchmaking for the Ashtakoot score out of 36 with the eight kootas, dosha flags and cancellations, and read classical_vetoes before you display anything: when Rajju or Vedha is present, the classical tradition treats the match as incompatible whatever the score. South Indian platforms add Dashakoot, Papasamyam and the Kerala or Tamil porutham endpoints on the same key.
Endpoints, in order: GET /v1/utils/geocode, POST /v1/astro/matchmaking, POST /v1/astro/matchmaking/papasamyam, POST /v1/astro/matchmaking/porutham (optional). Worked request and real response on the kundli matching API page; full walkthrough in the matrimonial platform guide; a working Next.js repo in Vedic matchmaking in Next.js.
2. An AI astrologer that works from real charts
Language models cannot compute planetary positions, so the assistant collects birth details, calls Asterwise, and explains the structured result. The recommended sequence is the natal chart with include_interpretation for pre-written context, then yogas, doshas, the current dasha at two levels, and transits. If your product runs on Claude, Cursor or another MCP client, connect the MCP server instead and the assistant calls the same calculations as tools, read-only, over OAuth, with no integration code.
Endpoints, in order: POST /v1/astro/natal, POST /v1/astro/yoga, POST /v1/astro/dosha, POST /v1/astro/dasha, POST /v1/astro/gochar. Guide: AI astrology chatbot integration. Background: what an astrology MCP server is.
3. A daily horoscope or panchang feed
The simplest integration needs no birth data. GET /v1/horoscope/daily/{moon_sign} serves Moon-sign horoscopes, with weekly, monthly and yearly variants and a Western sun-sign set under /v1/western/horoscope/; fetch all twelve signs once a day and cache them. For a panchang widget, POST /v1/astro/panchanga returns tithi, vara, nakshatra, yoga and karana with end times for any date and place, with Choghadiya, Rahu Kaal, the monthly calendar and the festival calendar as sibling endpoints.
Endpoints: GET /v1/horoscope/daily/{moon_sign}, POST /v1/astro/panchanga, POST /v1/astro/panchanga/choghadiya, GET /v1/astro/panchanga/festivals. Worked request on the panchang API page; a no-code version in the n8n daily panchanga bot.
4. A natal chart and dasha dashboard
Two calls give you a chart screen: POST /v1/astro/natal for the data (nine grahas with nakshatra, both house conventions, drishti, arudha padas) and POST /v1/astro/chart for the same chart as inline SVG, North Indian and South Indian style, for D1 and D9. POST /v1/astro/dasha with levels: 2 returns Mahadasha and Antardasha with dates, and its interpretation block names the current periods so the timeline can highlight them; go to five levels when the product times events.
Endpoints: POST /v1/astro/natal, POST /v1/astro/chart, POST /v1/astro/dasha, then POST /v1/astro/yoga, POST /v1/astro/dosha and POST /v1/astro/gochar as the product grows. Pages: Vedic astrology API and Vimshottari dasha API; guide: build an astrology app.
What every one of these gets
The same engine and the same answer for the same input, HMAC-signed responses, positions checked against NASA JPL Horizons on the accuracy page, Python and TypeScript SDKs generated from the OpenAPI document, and a per-call price you can compute before you build on the pricing page. Western products get the tropical set on the Western astrology API page with the same key.
Questions developers ask
- How do I add kundli matching to my app?
- Collect both birth details, resolve the city names to coordinates and a timezone with GET /v1/utils/geocode, then call POST /v1/astro/matchmaking. The response carries the Ashtakoot score out of 36, the eight kootas, dosha flags with cancellations, and Rajju and Vedha as explicit vetoes. Check the vetoes before you show the score. Dashakoot, Papasamyam and the Kerala and Tamil porutham systems are separate calls on the same key. Kundli matching API.
- Can I build an AI astrologer with this?
- Yes. Language models cannot compute planetary positions, so the pattern is: your assistant collects birth details, calls Asterwise for the chart, dasha, yogas, doshas and transits, and then explains the structured result. With Claude, Cursor or any MCP client you skip the integration entirely: the MCP server exposes 103 read-only tools over OAuth. Connect an AI client.
- What does a daily horoscope or panchang feed need?
- For Moon-sign horoscopes, GET /v1/horoscope/daily/{moon_sign} needs no birth data; the weekly, monthly and yearly variants and the Western sun-sign set work the same way. For a panchang widget, POST /v1/astro/panchanga returns the day's tithi, vara, nakshatra, yoga and karana with end times for any date and place; cache the result per city per day. Panchang API.
- How do I show a natal chart and a dasha timeline?
- POST /v1/astro/natal returns the chart data; POST /v1/astro/chart returns the same chart as SVG in North Indian and South Indian style for D1 and D9, ready to inline. POST /v1/astro/dasha with levels 2 gives Mahadasha and Antardasha with dates, and its interpretation block names the current periods so you can highlight them. Vimshottari dasha API.
- Is there a free tier for building and testing?
- Yes. The Sandbox plan is free, includes 500 calls a month and every endpoint, needs no credit card and does not expire. What the free tier covers.
Start with 500 free calls a month, no card, no expiry. Every plan includes all 118 endpoints. Create a key or see pricing.