WordPress chat integration
Connect WordPress to the same authenticated host page used by your web and mobile clients.
Install the Vedika Astrology plugin
The Vedika Astrology plugin is listed in the WordPress plugin directory. Install it from WordPress.org, or open Plugins > Add New Plugin in WordPress, search for Vedika Astrology by vedikaintelligence, then install and activate it. It adds horoscope, tarot, panchang, birth chart, compatibility and numerology as shortcodes, blocks and widgets, and shows sample data until you save your own Vedika key. The full guide is in the plugin documentation.
Pricing. The plugin itself is free. Live data uses your own Vedika key; see current plans on the pricing page.
The plugin is a widget plugin and does not include authenticated chat. For chat on WordPress, use the Custom HTML setup below.
Custom HTML setup
Add a Custom HTML block to the page in the block editor, paste the launcher below and publish. The launcher opens your independently authenticated chat page.
<!-- WordPress Custom HTML block -->
<a href="https://chat.example.com/chat" target="_blank" rel="noopener">
Open your account’s chat
</a>Build the chat page
Your team hosts https://chat.example.com/chat, implements the authenticated backend ticket endpoint, then installs the module-loader example on that page. Authenticate the user there with your application’s own sign-in. Never put a server key or mint token in a platform block or URL.
Allowed origin and renewal
Save the exact HTTPS origin of your chat host page in Integrations → Allowed sites, then publish branding. Its loader calls your backend through getSession, with independently pinned verification keys. Return fresh ticket, nonce and signedConfig values for the same signed-in user, with Cache-Control: no-store. The loader owns ticket redemption and its in-memory chat session.
Before production
Test the published WordPress launcher, sign-in, first turn, Stop, history, receipts, renewal and logout. If nesting your host page, allow every ancestor site origin too and test browser cookie restrictions; a top-level launcher avoids third-party sign-in dependencies. Use Getting started and Support for provisioning help.