Partner Account
Complete Configuration & Setup Guide

A Partner account allows you to embed HolyExplorer's Biblical AI widgets directly into your own website or application. Instead of sending your users to HolyExplorer.com, you bring the tools — AI Theological Chat, Bible Explorer, Bible Reader, and Bible Digital Media — right into your site.

Partner accounts are for:

• Churches, ministries, and religious organizations
• Christian education websites and learning platforms
• Catholic and denominational resource sites
• Developers building Biblical content into third-party platforms

When you log in to HolyExplorer.com, all partner tools are accessed through the hamburger menu (the three-line icon ≡ in the top-right corner of the page). Tapping or clicking it opens a navigation panel with the following structure:

Before creating your first widget configuration, set up your organization information. This establishes your primary authorized domain — the website where your embed code will be used.

To update your organization settings:

1. Open the hamburger menu (≡, top-right corner)
2. Under Partner Tools, click Organization Settings
3. Enter your organization name (this appears in widget headers and attribution)
4. Enter your primary domain (e.g., yourchurch.com — no https://, no trailing slash)
5. Save your changes

HolyExplorer offers five widget types. You can create separate configurations for each type depending on what your site needs.

Each configuration is a named set of settings that produces a unique embed code snippet. You can create multiple configurations — for example, one for your home page and a different one for your study guide section.

To create a new configuration:

1. Open the hamburger menu (≡, top-right corner)
2. Under Partner Tools, click My Configurations
3. Click Create New Configuration
4. Fill in the configuration fields (described below)
5. Click Save Configuration

Configuration Fields

Config Name (required)

A descriptive label for this configuration. This does not appear to your site visitors — it is only used in your dashboard to identify the configuration. Example: Home Page Full Suite or Bible Study Chat.

Widget Type (required)

Select one of the five widget types described in Section 4. The form will adjust based on your selection — the AI Vendor and AI Model fields are hidden for Bible Explorer since it does not use AI.

AI Vendor (required for AI-powered widget types)

Select the AI provider that will power the theological responses. Options: Gemini, OpenAI, or Anthropic. All three are capable theological AI systems. Gemini is the platform default if you leave the field on system default.

AI Model

The specific model from your selected vendor. The dropdown populates automatically after selecting a vendor. For most partners, the system default model is recommended unless you have specific requirements.

Default Denomination

Sets the theological lens for AI responses. This affects how Scripture is interpreted and which traditions are referenced. Options include Catholic, Baptist, Lutheran, Methodist, and many others. Default: Catholic.

Bible Translation

Controls which translation appears in Bible Explorer and Bible Reader. ALL shows a multi-translation view. Alternatively, select a specific translation (KJV, NIV, NABRE, etc.) to display that version only.

Title

The heading text displayed at the top of the widget. Keep it brief. Default values are provided per widget type.

Placeholder Text

The prompt text shown inside the chat input field before the user types. Example: Ask me anything about the Bible...

Welcome Message

The first message the widget displays when it loads. Use this to orient your visitors. Example: Welcome! I'm here to help with questions about Scripture, Catholic doctrine, and Biblical history.

Use Fixed Height Container (optional)

By default, the widget uses a flexible minimum height of 550px and expands as needed. Enable this option and enter a specific pixel value (e.g., 700) to lock the widget to a fixed height. Useful when embedding inside a precisely sized page section.

Enable Hash Routing (optional)

When enabled, the widget uses URL hash fragments (#chat, #bible-explorer, etc.) to track the active tab. Useful if you want to link directly to a specific tool within the Full Suite widget from other pages on your site.

After saving a configuration, you can generate the embed code snippet to paste into your website.

To generate embed code:

1. Open the hamburger menu (≡, top-right corner)
2. Under Partner Tools, click My Configurations
3. Find your configuration in the list and click the Get Embed Code button next to its name
4. A modal dialog will appear showing your API key and the embed code snippet

What the Embed Code Looks Like

A typical Full Suite embed code looks like this:

<!-- Configuration: My Church Widget -->
<div id="angelai-chat" style="width:100%;min-height:550px;border:0px solid #ddd;border-radius:5px;"></div>
<script>
    window.angelAiConfig = {
        "apiKey": "your-api-key-here",
        "organizationName": "My Church",
        "title": "BibleAngelAI Suite",
        "placeholder": "Choose your preferred tool...",
        "widgetType": "all",
        "theme": "light",
        "denomination": "Catholic",
        "translation": "ALL",
        "apiBase": "https://your-backend-url.replit.app"
    };
    (function() {
        var script = document.createElement('script');
        script.src = window.angelAiConfig.apiBase + "/embed/chat-widget.js";
        script.async = true;
        document.head.appendChild(script);
    })();
</script>

The embed code is standard HTML and JavaScript. It works on any website platform — WordPress, Squarespace, Webflow, custom HTML sites, or any other CMS that allows you to paste HTML into a page.

WordPress Sites

No plugin is required. Use any method that lets you insert raw HTML on a page:

1. Copy your embed code from the modal
2. In the WordPress block editor (Gutenberg), add a Custom HTML block to the page where you want the widget and paste the embed code into it. In a page builder like Divi or Elementor, add a Code module and paste there.
3. Publish or update the page

All Other Platforms

1. Copy your embed code from the modal
2. Paste the full snippet — both the <div> tag and the <script> block — into the HTML of the page at the location where the widget should appear
3. The widget will load asynchronously and render inside the <div id="angelai-chat"> container

Placement Tips

• The widget renders in-place wherever you position the <div> element. Give it a containing column or section with appropriate width.
• For a full-width experience, wrap the <div> in a 100%-wide container.
• For a sidebar placement, the widget will adapt to the container width but functions best at 400px or wider.
• The widget does not create a floating or pop-up overlay — it is an inline content widget that sits within your page layout.

Your API key only works on domains you have explicitly authorized. This prevents your API key from being used on unauthorized sites if someone discovers it in your page source.

Primary Domain

Your primary domain (set in Organization Settings) is always authorized. You cannot remove it without updating your organization settings.

Adding Additional Authorized Domains

You may need to authorize additional domains in these scenarios:

• A staging or development environment (staging.yourchurch.com)
• A subdomain that runs separately from your main site (resources.yourchurch.com)
• Multiple websites under your partner account

To add additional domains:

1. Open the hamburger menu (≡, top-right corner)
2. Under Partner Tools, click My Configurations
3. Open the configuration creation or editing form
4. In the Additional Authorized Domains field, enter one domain per line (no https://, no trailing slash)
5. Save the configuration — the additional domains take effect immediately

Domain Authorization Errors

If your widget loads but shows an authorization error, check:

• The domain in your browser's address bar matches exactly what is listed in your authorized domains
• You are not using a protocol prefix (https://) or trailing slash — enter bare domains only
• Subdomains must be listed explicitly — authorizing yourchurch.com does not automatically cover www.yourchurch.com or staging.yourchurch.com

Your API key is the credential that authenticates requests from your embedded widgets to the HolyExplorer backend.

Key facts about your API key:

• It is automatically generated when your partner account is created
• It is visible in the Get Embed Code modal — look for the field labeled API Key
• All widget configurations under your account share the same API key
• Every API call made through your widgets consumes credits from your account balance

How Credits Work

HolyExplorer operates on a credit system. Every AI-powered interaction (chat response, Scripture explanation, image generation, video generation, audio narration) consumes credits. The number of credits consumed varies by:

• AI operation type — image and video generation consume more credits than chat responses
• AI model selected — more powerful models consume more credits per request
• Response length — longer AI responses consume more credits

Monthly Subscription Credits

Your partner subscription plan includes a monthly credit allocation. These credits refresh at the start of each billing cycle and do not roll over to the next month.

Your current plan details — including monthly credit allocation, renewal date, and current balance — are visible under Billing → Plans in the hamburger menu.

Top-Up Credits

If your monthly allocation runs out before the end of the billing period, you can purchase top-up credits. Top-up credits:

• Are added to your balance immediately after purchase
• Do not expire — they carry forward indefinitely
• Are consumed after your monthly subscription credits are depleted

To purchase top-up credits, open the hamburger menu, go to Billing → Payment, and look for the Purchase Top-Up Credits option.

Monitoring Usage

Billing → Usage in the hamburger menu shows your current credit balance and historical usage by date and operation type. If you anticipate high traffic to your embedded widgets, monitor this section regularly.

What Happens When Credits Run Out

• Chat and AI-powered features stop responding and display a service unavailable message
• Credit-free features (Bible Explorer search, Bible text display) continue working
• Purchase top-up credits or wait for your monthly allocation to refresh to restore full functionality

HolyExplorer partner plans are structured around usage volume:

• Entry-level partner plan — Lower monthly credit allocation. Appropriate for small sites or initial setup.
• Standard and higher partner plans — Higher monthly credit allocations, suitable for active sites with regular visitor traffic.

Your current plan and tier are shown under Billing → Plans in the hamburger menu. To upgrade, select a higher plan from the plan listing — you will be directed through a Stripe checkout flow.

You can create as many configurations as your account requires — one per page, per site section, or per widget type. They all share the same API key but each can have different settings (different widget types, denominations, AI vendors).

Best practices for multiple configurations:

• Name configurations clearly, including the site location and widget type (e.g., Home Page - Full Suite, Study Guide - Chat Only, Devotional - Bible Reader)
• Create separate configurations for staging/development environments so that you can adjust settings without affecting your live site
• Review unused configurations periodically and delete any that are no longer in use — each active configuration on your site is generating API traffic that consumes credits

Widget Does Not Appear on My Page

• The embed code is pasted correctly and completely — both the <div> tag and the full <script> block must be present
• The page domain is listed in your authorized domains
• No JavaScript errors appear in your browser console (right-click → Inspect → Console tab)
• Your credit balance is not zero

Widget Shows "Temporarily Unavailable"

This typically means the backend could not be reached, or a network/firewall issue is blocking the script from loading.

• Your hosting provider does not block outbound requests to external script sources
• Any Content Security Policy (CSP) headers on your site allow the HolyExplorer backend URL as a script source
• The widget is not being blocked by a browser extension (ad blockers, privacy tools) in your test environment

Authorization Error / "Invalid API Key"

• The apiKey value in your embed code exactly matches the API key shown in your dashboard
• You have not accidentally introduced extra spaces or line breaks when copying the embed code
• Your domain is in the authorized domains list

Chat Responses Seem Wrong or Off-Topic

• The Default Denomination setting matches what your audience expects — switching from Catholic to a different denomination will change how Scripture is interpreted in AI responses
• If you selected a specific AI vendor or model, try switching to a different one to compare results
• Your Welcome Message and Placeholder text can implicitly set expectations — clear framing helps the AI understand the intended context

Credits Running Out Quickly

• Check Billing → Usage in the hamburger menu — look for unexpected spikes in usage, which may indicate a misconfigured page or bot traffic hitting the widget
• Consider switching to a less credit-intensive AI model for chat if your primary use case is simple Q&A rather than complex theological analysis
• Consider limiting the widget to credit-free modes (Bible Explorer only) on high-traffic pages

If you encounter an issue not covered in this guide:

• Use the HolyExplorer AI Assistant (the chat bubble at the bottom-right of your screen when logged in) — it has access to your account data and can answer questions about your credits, subscription, and configuration.
• Contact HolyExplorer support directly through your account page.