Migrate to Vedika

Moving from another astrology or LLM API? Map your integration onto Vedika concept by concept.

Moving to Vedika from another astrology or LLM API? The core concepts map over directly. This page is a concept-by-concept guide for porting an existing integration — swap a handful of names, add one required field, and you are calling Vedika.

#Concept mapping

If your current provider exposes an OpenAI-shaped chat/completions endpoint (or something similar), the table below is the direct translation. OpenAI is named here only as the external wire-format standard being mapped from — not a claim about what powers Vedika; Vedika's own tiers use masked product-tier names only, as everywhere else in these docs.

#Migration steps

1. Get a key

   Create a Vedika API key from the dashboard — see API Keys.

2. Swap the base URL and auth header

   Copycurl -s https://api.vedika.io/api/v1/astrology/query \
     -H "x-api-key: $VEDIKA_KEY"

3. Add birthDetails to every request

   Vedika requests carry a birthDetails object alongside the question — see Key differences below for why.

4. Map your model selection to a tier

   Replace a model-name field with speed (and, optionally, version) as shown in the mapping table above.

5. Test in the sandbox first

   Point the same request shape at the keyless mock sandbox before switching in a live key — no charge, no key required.

#Key differences

The one structural difference: Vedika grounds every answer in a computed birth chart, so a request carries birthDetails, not just a prompt. The chart comes back on the response too, as birthChart, so you and your users can see what the answer is grounded in. See AI Query for the full request/response contract.