The astrology backend for your app.

What is the Vedika astrology API?

Vedika is an astrology API for developers. One authenticated base URL, https://api.vedika.io, returns structured chart data and natural-language readings for Vedic (sidereal), Western (tropical) and KP calculations, with Vastu, Tarot, Numerology and other systems on the same key. The astrology API endpoint reference lists what each route returns.

Is there a free astrology API?

There is no free production tier. A keyless mock sandbox mirrors the production routes so you can try request and response shapes, and accounts that have never paid can start one 14-day Professional trial. Plans start at $12/month.

Is the sandbox the same as production?

No. The keyless sandbox is an illustrative fixture surface for learning request and response shapes. It is not paid production access, does not promise production capacity, and must not be used to infer a live entitlement.

How do I make the first authenticated request?

Create an account, issue an API key, choose a documented route, and send the key in the required request header. Start with the quickstart, then use the API reference as the authority for fields, response objects, and current versions.

What does an AI astrology query return?

The documented pattern accepts a natural-language question plus birth details. The response separates the generated interpretation from computed chart context and includes public metadata such as the intelligence engine and ephemeris data source.

Which delivery engine should I use?

Eco and Standard cover the lower-cost query path. Swift is listed for Business and Enterprise. Vedika Pro Ultra is plan dependent, and Vedika Ephemeris uses a contract rate. Select against latency, quality, and the current contract—not a marketing label alone.

What are the exact rate limits and endpoint limits?

Limits are contract-governed. The public wallet price does not by itself define concurrency, endpoints, streaming, reports, team seats, support, or an SLA. Confirm those values in the signed plan terms before designing capacity.

Can I build a real-time Voice AI product?

Yes. Voice experiences can use the same computed context as text interpretation, with playback, transcript, and conversational controls in your product. Streaming modes, supported languages, latency targets, and limits follow the live surface and contract.

Can Vedika generate branded PDF reports?

The report flow combines a report type, birth details, language, and optional brand inputs, then returns a report result for delivery. Use the report documentation for supported formats and keep generation, preview, and download states explicit in your UI.

Which languages are available?

Supported V2 routes accept up to 30 language codes, but coverage differs by feature and delivery mode and output can fall back to English. Verify the exact route and language on the current live surface before you publish coverage.

Which astrology systems does the API support?

Vedic (sidereal, Jyotish), Western (tropical) and KP (Krishnamurti Paddhati) calculations are available in one API, alongside Vastu, Tarot, Chinese astrology, Numerology, Lal Kitab, Jaimini and other domains. Coverage varies by route; the API reference shows each one.

Do you provide SDKs, MCP, and agent integrations?

Yes. Use the JavaScript or Python SDK for application code, and the Vedika MCP server (npx @vedika-io/mcp-server) so MCP-compatible AI assistants, agents and code editors can call the API as tools with your key. Keep the OpenAPI schema and versioned reference in the loop so generated clients and tool definitions remain aligned with the live contract.

How should I handle versions and migrations?

Pin the documented version, validate response fields in staging, and read the changelog before moving traffic. Do not depend on an example fixture as a permanent schema. The API reference and changelog are the two sources to check together.

How do webhooks and asynchronous delivery fit?

Use webhooks when a documented workflow finishes outside the request window, such as delivery-oriented report flows. Verify event names, signature checks, retry behavior, and idempotency in the current webhook documentation before enabling production.

Where can I test a request before coding the full UI?

Use the sandbox for safe illustrative fixtures, the API Explorer for endpoint inspection, and the Playground for request examples. Move to a production key only after your error, loading, retry, and empty states work.

How do I monitor service health and get support?

Check the status surface for service health and use support for account or integration issues. Enterprise response times and service terms are contractual; the public site must not be read as an unstated SLA.

What should I review for security and data handling?

Keep keys server-side, scope access to the product need, avoid logging secrets, and review the current security and privacy terms for retention and processing obligations. Your own app remains responsible for consent and safe handling of birth data.

What is the difference between Lite and Experience?

Lite keeps the same Vedika product map, real links, demos, plans, and documentation paths with lower graphics and scroll cost. Experience is the cinematic black-hole journey. The switch preserves that choice without changing your account or API access.