Agent Platform1

AI & MCP7

AI Interpretations5

AI Reports5

Aspects & Points11

Astro-Geography18

BaZi (Four Pillars)11

Business Astrology12

Calendar & Cycles15

Chinese: Zodiac & Feng Shui14

Comparisons10

Content Localization4

Core4

Cosmobiology / Hamburg School10

Destiny Matrix1

Dignities & Receptions6

Elder Futhark Runes5

Embeddable Widgets14

Esoteric17

Evolutionary Astrology5

Family Astrology5

Financial Astrology10

Geomancy (Agrippa)16

Hellenistic: Brennan tradition10

Hellenistic: Greenbaum tradition10

Hellenistic: Hand tradition10

Hellenistic: Schmidt tradition10

Horary6

Horoscope5

Human Design12

I Ching (Standalone)5

Kabbalah3

Mayan Calendars8

MCP Advanced5

Modern Psychological15

Numerology: Chaldean10

Numerology: Kabbalistic (Mathers strict)10

Numerology: Kabbalistic (phonetic)10

Numerology: Pythagorean10

Numerology: Vedic10

Palmistry (Cheiro)5

Pet Astrology14

Prognostics15

Public9

Real-time Streaming10

Reference14

Reports18

Specialized Charts5

System6

Tarot: Lenormand10

Tarot: Marseille21

Tarot: Rider-Waite-Smith35

Vedic174

Visualization14

Webhooks15

Wellness10

White-label5

Zi Wei Dou Shu (Purple Star): MVP13

Zodiac Signs (Per-Sign Deep)12

AI Interpretations

Synastry Interpretation

AI interpretation of synastry between two charts: relationship dynamics, attractions, friction points, long-term outlook.

post/interpret/synastry

Query parameters

lang'uk' | 'en' | 'de' | 'ru' | 'pl' | 'es' | 'pt' | 'fr' | 'it' | 'nl' | 'cs' | 'ro' | 'hu' | 'el' | 'tr' | 'ar' | 'hi' | 'ja' | 'ko' | 'vi' | 'id'

Alternative to Accept-Language for clients without header control.

Headers

Accept-Language'uk' | 'en' | 'de' | 'ru' | 'pl' | 'es' | 'pt' | 'fr' | 'it' | 'nl' | 'cs' | 'ro' | 'hu' | 'el' | 'tr' | 'ar' | 'hi' | 'ja' | 'ko' | 'vi' | 'id'

Target language for response text fields. RFC 7231 q-weighted. Falls back to ?lang= query param, then body.language, then source uk. Unknown codes silently fall through to uk.

Bring your own model key: the LLM provider that should run this completion. Send together with X-Provider-Key or the request is refused: a key with no provider bills us for tokens you meant to pay for, and a provider with no key would look like it worked. The endpoint is fixed per provider on our side and is never taken from the request. There is no fallback to our own chain: if your key fails you get the provider's status and message.

X-Provider-Keystring

Your own credential for X-Provider. Never logged, stored or cached: it travels in a header because the request body is hashed into two cache keys, and a BYOK turn bypasses both caches in each direction. A provider error that quotes the key back is redacted before it reaches our logs or your response. Such a turn costs 5 credits instead of the endpoint price, and only when a completion actually ran on your key.

X-Provider-Modelstring

Optional model id, overriding the default for that provider. Defaults: openai → gpt-4o-mini, anthropic → claude-sonnet-4-5, google → gemini-2.5-flash, groq → llama-3.3-70b-versatile, mistral → mistral-large-latest, openrouter → meta-llama/llama-3.3-70b-instruct, deepseek → deepseek-chat, together → meta-llama/Llama-3.3-70B-Instruct-Turbo.

Request body

language'uk' | 'en' | 'de' | 'pl' | 'es' | 'pt' | 'fr' | 'it' | 'nl' | 'cs' | 'ro' | 'hu' | 'el' | 'tr' | 'ar' | 'hi' | 'ja' | 'ko' | 'vi' | 'id' | 'ru'

disclaimer_inlineboolean

Response

Successful calculation

okboolean

Example response

{
  "ok": true
}

Changes

Changed in 4 of the 13 revisions of this API.81512

Aug 23, 2026529d7d36d7d633See the full diff
- ●
  removed the optional property data/dynamics from the response with the 200 status
  response-optional-property-removed
- ●
  removed the optional property data/outlook from the response with the 200 status
  response-optional-property-removed
- ●
  removed the optional property data/summary from the response with the 200 status
  response-optional-property-removed
- ○
  added the optional property data/disclaimer to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property data/interpretation to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property data/model to the response with the 200 status
  response-optional-property-added
Aug 18, 2026dd3764875e7a2See the full diff
- ○
  added the new optional request property allOf[TwoChart]/chart1/ayanamsa
  new-optional-request-property
- ○
  added the new optional request property allOf[TwoChart]/chart2/ayanamsa
  new-optional-request-property
Aug 15, 2026e637d1a9911b43See the full diff
- ●
  the allOf[TwoChart]/chart1/timezoneOffset request property's max was set to 14.00
  request-property-max-set
- ●
  the allOf[TwoChart]/chart2/timezoneOffset request property's max was set to 14.00
  request-property-max-set
- ●
  the allOf[TwoChart]/chart1/timezoneOffset request property's min was set to -14.00
  request-property-min-set
- ●
  the allOf[TwoChart]/chart2/timezoneOffset request property's min was set to -14.00
  request-property-min-set
- ○
  added the new optional header request parameter X-Provider
  new-optional-request-parameter
- ○
  added the new optional header request parameter X-Provider-Key
  new-optional-request-parameter
- ○
  added the new optional header request parameter X-Provider-Model
  new-optional-request-parameter
Aug 11, 2026b0533bcc12c0884See the full diff
- ▲
  the request property allOf[TwoChart]/chart1/latitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property allOf[TwoChart]/chart1/longitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property allOf[TwoChart]/chart2/latitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property allOf[TwoChart]/chart2/longitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property allOf[TwoChart]/chart1/latitude became required
  request-property-became-required
- ▲
  the request property allOf[TwoChart]/chart1/longitude became required
  request-property-became-required
- ▲
  the request property allOf[TwoChart]/chart2/latitude became required
  request-property-became-required
- ▲
  the request property allOf[TwoChart]/chart2/longitude became required
  request-property-became-required
- ●
  the allOf[TwoChart]/chart1/latitude request property's max was set to 90.00
  request-property-max-set
- ●
  the allOf[TwoChart]/chart1/longitude request property's max was set to 180.00
  request-property-max-set
- ●
  the allOf[TwoChart]/chart2/latitude request property's max was set to 90.00
  request-property-max-set
- ●
  the allOf[TwoChart]/chart2/longitude request property's max was set to 180.00
  request-property-max-set
- ●
  the allOf[TwoChart]/chart1/latitude request property's min was set to -90.00
  request-property-min-set
- ●
  the allOf[TwoChart]/chart1/longitude request property's min was set to -180.00
  request-property-min-set
- ●
  the allOf[TwoChart]/chart2/latitude request property's min was set to -90.00
  request-property-min-set
- ●
  the allOf[TwoChart]/chart2/longitude request property's min was set to -180.00
  request-property-min-set
- ○
  the latitude request property default value 0 was removed
  request-property-default-value-removed
- ○
  the latitude request property default value 0 was removed
  request-property-default-value-removed
- ○
  the longitude request property default value 0 was removed
  request-property-default-value-removed
- ○
  the longitude request property default value 0 was removed
  request-property-default-value-removed

Full history