AIgency 2.0

A multi-model AI chat you run on your own hosting and sell with your own brand, prices and plans.

Overview

The package contains:

FolderWhat it is
aigency/Version 2.0, ready to upload. Dependencies and the compiled interface are included: you do not need SSH, Composer or Node.
documentation/This guide.
THIRD-PARTY-LICENSES/The licenses of the libraries, font and images included (see Third-party licenses).

Your customers chat with models from OpenAI, Anthropic and Google (and OpenAI-compatible providers such as xAI, DeepSeek and OpenRouter), can compare two models side by side, and pay with credits. You decide which models are offered, how much each one costs and how credits are sold.

Support and custom work: willian@polargames.com.br. Please include your purchase code and what you see (a screenshot and the text of the error help a lot).

Requirements

The installer checks every item and tells you what to change before anything is written.

Installation

  1. Create an empty MySQL database and a user for it in your hosting panel. Write down host, database name, user and password.
  2. Upload the contents of aigency/ to the folder where the site will live: the domain root (for example public_html/) or a subfolder (public_html/chat/). Uploading a ZIP and extracting it with the panel's file manager is fastest.
  3. Open the site in the browser. You are sent to /install.
  4. Check the requirements list. Red items must be fixed; yellow items are recommendations.
  5. Fill in the database details and your admin account (name, e-mail, a password of at least 12 characters) and click Install. Tables are created and example models and assistants are added.
  6. Sign in with the admin account. The installer is disabled from now on (it answers "not found").
Pointing the domain to public/ (optional, recommended when your panel allows it). The package works when the whole folder is uploaded to the web root: the included index.php and .htaccess send every request to public/ and block access to configuration files. If your panel lets you choose the document root, point it to the public/ folder instead.

Nginx

root /path/to/aigency/public;
location / { try_files $uri $uri/ /index.php?$query_string; }
location ~ \.php$ { include fastcgi_params; fastcgi_pass unix:/run/php/php8.4-fpm.sock; # your PHP version
  fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
  fastcgi_buffering off; }   # answers are streamed word by word

Speed

public/.htaccess compresses text and lets browsers keep the built files for a year (their names change with every version) and images for a week. Specialist photos have 160 and 320 px copies next to them, used where the photo is shown small; after adding or replacing portraits in public/assistants/specialists by hand, run php artisan aigency:avatar-sizes to make their copies (photos uploaded in the admin work without them).

Shared hosting notes (Hostinger, cPanel)

AI providers and models

Go to Admin → Models.

  1. Paste the API key of each provider you want to use and click Test connection. Keys are stored encrypted with your site's APP_KEY; after saving, only the last four characters are shown.
  2. Activate the models you want to offer. A model without prices cannot be activated.
  3. Adjust the margin of each model (see the next section).
ProviderWhere to get a key
OpenAIplatform.openai.com → API keys
Anthropic (Claude)console.anthropic.com → API keys
Google (Gemini)aistudio.google.com → Get API key
xAI, DeepSeek, OpenRouterThe provider's console. These use the OpenAI-compatible adapter; add prices before activating.

Image generation uses an image model (for example gpt-image-2.5-flare) and is charged by the real usage reported by the provider.

Credits and pricing

Customers spend credits. Each answer costs:

credits = provider cost in US$ × credits per US$ × model margin   (rounded up)

Before an answer starts, the maximum possible cost is reserved; when it ends, only the real cost is charged and the rest returns to the balance. A failed or cancelled answer that produced nothing costs nothing. The Admin → Models page shows the credits of a typical message for each model so you can check your prices.

Billing: packs, plans, mixed

In Admin → Plans & billing choose how you sell:

ModeHow it works
Credit packsCustomers buy credits once. Purchased credits do not expire. Every active model is available.
SubscriptionMonthly or yearly plans that grant credits each cycle and define which models are included. Unused plan credits expire, carry over up to a cap, or accumulate, as you configure per plan.
Mixed (default)Plans plus packs. Plan credits are spent first. A model outside the customer's plan can still be used with purchased credits (the chat shows a lock and explains why).

Packs may include bonus credits. Every movement is recorded in an append-only ledger that customers see on their Usage page.

What each plan opens

In Admin → Plans & billing → Prices, each plan says:

A locked specialist shows "On the X plan" in the catalog, and opening it shows an upgrade card with the plans that include it. Purchased credits do not unlock it: it is an upgrade. In "credit packs only" billing nothing is locked.

Monthly and yearly prices

A plan can be charged monthly, yearly or both. Turn on Charge yearly and set a Yearly discount (%): the yearly price is worked out as 12 monthly payments minus the discount, and you can still type the exact yearly price (the saved yearly price is what customers pay). Each interval has its own credits per cycle. The pricing page and your home page show a Monthly / Yearly switch with "Save N%" and the price per month billed yearly. Turning an interval off hides it from new customers; current subscribers keep it.

Stripe

  1. In the Stripe dashboard, copy your secret key (sk_live_…, or sk_test_… while testing).
  2. Create a webhook endpoint pointing to https://your-site/webhooks/stripe with these events: checkout.session.completed, invoice.paid, invoice.payment_failed, customer.subscription.updated, customer.subscription.deleted. Copy its signing secret (whsec_…).
  3. Paste both in Admin → Plans & billing → Payments → Stripe and save. They are stored encrypted; the page shows the webhook URL and the event list to copy into Stripe. (Alternatively, set STRIPE_SECRET_KEY and STRIPE_WEBHOOK_SECRET in .env; values saved in the admin take precedence.)
  4. In Admin → Plans & billing → Prices, create your packs and plans with prices.

Bank transfer (manual payment)

No gateway account needed. Open Admin → Transfers, turn it on and write the details customers should use (bank, account, Pix or IBAN, notes); you can add one text per language. Customers then see a "Bank transfer" button on every plan and credit pack, pay from their bank and upload the receipt (JPG, PNG, WebP or PDF, up to 5 MB).

Each order waits in the same page: open the receipt, then Approve (credits are added once, never twice) or Refuse with a reason. The customer gets an e-mail either way, so set up outgoing e-mail in Admin → Brand → E-mail first. A plan paid by transfer covers one period and does not renew by itself.

PayPal (credit packs and plans)

  1. At developer.paypal.com, create a REST app (Sandbox to test, Live to sell) and copy its Client ID and Secret. Selling plans needs a PayPal Business account.
  2. Paste them in Admin → Plans & billing → Payments → PayPal, choose the environment and save.
  3. For plans, add a webhook in the same PayPal app pointing to https://your-site/webhooks/paypal with the events shown on that card: BILLING.SUBSCRIPTION.ACTIVATED, BILLING.SUBSCRIPTION.CANCELLED, BILLING.SUBSCRIPTION.EXPIRED, BILLING.SUBSCRIPTION.SUSPENDED, BILLING.SUBSCRIPTION.PAYMENT.FAILED and PAYMENT.SALE.COMPLETED.

Credit packs need no webhook: the customer approves the payment on PayPal and the order is captured when they come back, after the owner and amount are checked. A payment PayPal holds for review shows as pending and is credited when it clears (checked again when the customer opens Plans & credits).

Plans: the PayPal product and plan are created for you the first time a customer subscribes (and again if you change the price, currency or interval). Each renewal is credited once, by the webhook or, if a webhook is missed, the next time the customer opens Plans & credits. The webhook only says which subscription changed; everything is re-read from PayPal's API, so a forged call credits nothing. PayPal has no customer portal: customers use Cancel subscription on Plans & credits and keep access until the end of the period they paid. One renewing subscription per customer at a time: to change plan on PayPal, cancel and subscribe again.

Safe crediting: credits are never granted from what the browser sends. When the customer comes back from Stripe, your server reads the payment from Stripe's API; the signed webhook does the same in the background. Both use the same unique key, so a purchase or renewal is credited once even if the customer reloads the page, the webhook arrives late or Stripe sends it twice. The paid amount is checked against the price. Subscribers manage or cancel their plan with Manage subscription on Plans & credits, which opens Stripe's own customer portal (turn the portal on once in the Stripe dashboard → Settings → Billing → Customer portal).

Testing a purchase before you go live

Before selling for real, buy something on your own site in test mode. No money moves, and you see the whole path: payment page, return to your site, credits on the Usage page and the e-mail.

  1. Stripe: in the Stripe dashboard turn on Test mode, copy the test secret key (sk_test_…) and create the webhook in test mode too (it has its own whsec_…). Save both in Admin → Plans & billing → Payments → Stripe. Sign in as a customer, open Plans & credits, choose a plan or a credit pack and pay with Stripe's test card 4242 4242 4242 4242, any future date, any CVC and any name. To see a refused payment use 4000 0000 0000 9995; for a card that asks for 3-D Secure, 4000 0025 0000 3155. Test subscriptions renew in Stripe's test clock, and the customer portal (Manage subscription) works in test mode as well.
  2. PayPal: choose Sandbox in the PayPal card and paste the sandbox app's Client ID and Secret. At developer.paypal.com → Sandbox accounts you will find a test buyer (a "Personal" account; set its password there). Buy on your site and log in to PayPal with that test buyer.
  3. Bank transfer: turn it on, buy as a customer with any image as the receipt, then approve it in Admin → Transfers.

Test purchases add real credits on your site: remove them in Admin → Customers (adjust credits) or use a test account. Going live: replace the Stripe keys with sk_live_… and a webhook created in live mode (new whsec_…), and switch PayPal to Live with the live app's keys. For a public demo of your site you can keep test mode on and tell visitors the test card (see Public demo mode).

Free preview (chat before signing up)

Visitors can talk to a specialist a few times before creating an account: on the public site, Chat opens the preview. When the free messages run out, a "Continue your conversation" window lets them sign up or sign in without leaving the page, and the conversation moves to their new account. Settings are in Admin → Plans & billing → Preview without account:

An answer that fails at the provider gives the free message back. In the preview the specialist makes no files and keeps no memory, and says so if asked. Free images are off by default: set "Free images per visitor" (for example 1 or 2) and, if you like, the preview's image model (default: the cheapest active image model with a key). Each image costs that model's price and counts toward the daily cap; an image the provider fails to make is given back.

Sign-up bonus per network: next to the welcome credits, "Bonuses per network (IP) in 30 days" (default 3, 0 = no limit) stops one person from making many accounts to collect the bonus. Schools and offices share one network, so raise it if your customers sign up from the same place.

For your privacy policy: the preview sets one functional cookie (aigency_preview, 30 days) that links the browser to its conversation; it is needed for the chat to work and is not used for analytics or advertising, so it does not depend on the cookie notice. The visitor's messages and the answers are stored on your server, with any images made there. The visitor's IP address is stored only as a keyed hash, to apply the limits above. Conversations and images of visitors who never create an account are deleted after 30 days; when the visitor signs up from the preview, the conversation and its images become part of their account. Suggested text: "You can try our specialists before creating an account. We store that conversation and a functional cookie for up to 30 days so you can continue it; if you create an account from it, the conversation is kept in your account."

Your brand

Outgoing e-mail

Sign-up confirmation, password reset, bank transfer notices and receipts are sent by e-mail. A fresh install only writes e-mails to a log file, so set this up before you open the site: Admin → Brand → E-mail.

Forgot password

"Forgot password?" on the login page sends a 6-digit code by e-mail. The customer types it on the same page together with the new password; there is no link to click. The e-mail carries your site name (APP_NAME) and brand colour and is written in the language the customer is using.

Languages

The interface ships in 14 languages: English, Español, Português (Brasil), Français, Deutsch, Italiano, Nederlands, Русский, Türkçe, العربية (right to left), हिन्दी, Bahasa Indonesia, 简体中文 and 日本語.

Areas (niche packs)

The same site can serve different audiences at once. An area is a group of specialists with its own banner: customers see a tab per area in the catalog (when two or more are on), with the area's headline and team photo. The installer installs the four areas below and asks which one the home page uses; switch off or delete in Admin → Areas the ones you do not want. Four areas ship with AIgency:

Managing areas

New specialists come in the language you are using in the admin when the pack has it (English and Brazilian Portuguese ship), else English.

Making your own pack

Create a folder database/packs/<key> (key: lowercase letters, digits and dashes) with a pack.json and, optionally, a photos/ folder (WebP, JPG or PNG; copied to public/assistants/packs/<key>/ when applied). Copy database/packs/school/pack.json as a starting point. Each text can be a plain string or an object by language ({"en": "…", "pt_BR": "…"}). A long description, welcome or instructions text can also be a list of pieces (["You are …, ", "and you …"]), as in the shipped packs: the pieces are joined with nothing in between, so keep the space at the end of a piece.

{
  "key": "clinic",
  "name": {"en": "Clinic"},
  "description": {"en": "Health information assistants."},
  "site": {"badge": {"en": "…"}, "title": {"en": "A *specialist* for every question"}, "subtitle": {"en": "…"},
           "hero": {"team": "assistants/packs/clinic/team.webp", "teamHero": "assistants/packs/clinic/team-arc.webp"}},
  "specialists": [
    {"slug": "clinic-nutrition", "sort": 1, "photo": "assistants/packs/clinic/nutrition.webp", "voice": "female",
     "name": {"en": "Nutritionist"}, "title": {"en": "Nutrition"}, "category": {"en": "Health"},
     "description": {"en": "…"}, "welcome": {"en": "…"}, "suggestions": {"en": ["…", "…"]},
     "skills": {"en": ["…"]}, "instructions": "You are … (in English; models answer in the user's language)"}
  ]
}

Slugs must be unique across all packs (prefix them with the pack key). *word* in the title is highlighted. Without site, the standard headline is used; give it in as many of the 14 languages as you can (missing ones fall back to your English). A broken pack.json is listed in Admin → Areas with the reason and is never installed. A new pack appears there as an area that is not installed yet.

site gives the home page headline (used when the pack is the home's area) and the catalog banner. To give an area a catalog banner without touching the home page, use "banner": {"badge": …, "title": …, "subtitle": …} instead: the banner wins in the catalog, and site stays the home headline. An optional previous.json next to pack.json lists older factory texts and photos ({"slug": {"instructions": […], "photo": […]}}) so Update texts can tell an old factory text from one you edited; you do not need it for a new pack.

Customers

Admin → Customers lists everyone with an account (preview visitors are not customers): plan, free credits, conversations, messages, last activity and sign-up date, with search by name or e-mail. Open a customer to:

For your privacy policy: administrators can read customers' conversations to provide support and prevent abuse. Every opening is recorded (which admin, which customer and conversation, when). Say this in your privacy policy, e.g. "Our staff may access your conversations to provide support or investigate abuse; each access is logged."

Admin overview

Admin → Overview is the first admin page: sign-ups and active customers per day, answers and the credits they used, recurring revenue per month (yearly plans count 1/12), active subscribers, purchases and renewals, provider cost and margin, where granted credits came from, top specialists and a live feed of recent activity. Each chart can be shown as a table. Amounts in other currencies are listed apart, not added.

Sample data: to see the admin full before you have customers (or for screenshots), run with SSH:

php artisan aigency:sample-data --customers=40 --days=30

It creates up to 40 sample customers (addresses at sample.example.com, a password nobody knows) with conversations, purchases and plans over the last days, through the real ledger, so they appear in Overview, Customers and Usage like real ones. No AI provider is called. Remove them before you open the site:

php artisan aigency:sample-data --remove

Specialists

Specialists are ready-made personas (instructions, welcome message, suggested questions, skills, voice and portrait) that work with any model. 150 come installed, grouped in four areas. A conversation started with a specialist keeps its instructions on every message, whichever model answers.

Edit them in Admin → Specialists: each row opens a side panel (texts, photo, category, voice, tools, visibility). The lock on a row makes that specialist only for plans that include it (see Plan access); the book icon opens its Knowledge page. You can create your own specialists; they belong to no area until you put them in one.

Knowledge base and AI employees

A specialist can answer from files and texts instead of general knowledge: Admin → Specialists, the book icon on a row opens its Knowledge page. Upload PDF, Word, Excel, PowerPoint, CSV or text files, or write questions and answers. Nothing is trained: on every question the passages that match are found and given to the model, and the answer cites them (customers click a source to see the passage). With Only from the base, a question the base does not answer gets your "I don't know" message with your contact, never a made-up answer.

For your privacy policy: files and texts in a knowledge base are sent to your AI provider in the passages of each answer (and, for the search by meaning, once when uploaded). Anything in a base can be told to whoever talks to that specialist. Administrators can open a customer's AI employee and its files from the admin (to provide support). Deleting a source, an employee or the account removes the files, passages and photo at once; past answers keep the text they already contained. Say this in your privacy policy, e.g. "Files you add to your AI employee are processed by our AI provider to answer questions and are deleted when you remove them."

Chat on your website

A specialist with a knowledge base can answer on any website: a chat button in the corner that opens the conversation in a small window. You can do it for your own specialists, and your customers can do it for their AI employees.

For your privacy policy: what visitors type on a website is stored as that specialist's site conversations and can be read by whoever owns the specialist. Your customers who put the chat on their sites should say so in their own privacy policy.

Chat features

Moving from 1.x

Version 1.x is deprecated and no longer included in the package. 2.0 is a new product: your 1.x data (customers, passwords, credits and assistants) moves in with the importer below.

Install 2.0 in a new folder and database (your 1.x site keeps working meanwhile). Then, with SSH access, run from the 2.0 folder:

LEGACY_DB_PASSWORD='your 1.x database password' php artisan aigency:import-legacy your_1x_database --dry-run

Options: --host=, --port=, --username=; --credits=paid (default: one old credit becomes one new credit) or --credits=usage --divisor=N (N old credits become one new credit). Remove --dry-run to import for real. A JSON report is saved in storage/app/private/.

On shared hosting, pass the 1.x database user (the default is root) and, if the php command is older than 8.3, call PHP by its path:
LEGACY_DB_PASSWORD='…' /opt/alt/php83/usr/bin/php artisan aigency:import-legacy u123_old1x --username=u123_old1x --dry-run
Both databases must be reachable from the 2.0 site (usually the same hosting account, host 127.0.0.1). Without SSH, ask your host to run the command, or contact support. After importing, Admin → Areas → Update texts gives the imported 1.x personas the rewritten 2.0 texts and portraits (your own edits are kept).
1.x2.0
CustomersUsers. Their 1.x passwords keep working: on the first sign-in the password is checked once and stored with modern hashing. E-mails that already exist in 2.0 are listed in the report and skipped.
Credit balancesAn opening entry in the ledger.
Prompts (personas)Assistants, with category and suggestions. A persona with the same slug as an example replaces it.
Credit packsImported hidden: check prices and credits, then activate them.
Chat historyConversations, with the old tone/style suffix removed from the messages.
Tone, writing style and output language menusNot needed in 2.0: every model answers in the language the customer writes in; a lasting preference ("always answer formally") goes in the customer's Memory and applies to every model; a persona's style goes in the assistant's instructions.

The 1.x database is only read. Running the command again skips users imported before.

Advanced settings

Optional lines in .env:

SettingDefaultMeaning
APP_NAMEset by installerSite name in the title, e-mails and pages.
AIGENCY_CREDITS_PER_USD10000Credits per US$ 1 of provider cost.
AIGENCY_PROFILEsharedvps raises the limits below.
AIGENCY_MAX_STREAMS12 (shared), 100 (vps)Answers being generated at once on the whole site. Shared hosting allows a limited number of PHP processes; extra requests wait their turn.
AIGENCY_PER_USER_ACTIVE2Answers one user can generate at once.
AIGENCY_CONTEXT_TOKENS24000How much recent conversation history (estimated tokens) is sent with each message. Older turns are left out, which keeps long conversations cheap and inside every model's limit.
AIGENCY_SILENCE_TIMEOUT90Seconds without data from a provider before the answer is stopped and refunded.
AIGENCY_DOCUMENT_MAX_KB10240Largest document a customer can attach, in KB.
AIGENCY_DOCUMENT_TOKENS30000How much of a document's text goes to the model on each message.
AIGENCY_KNOWLEDGE_EMBEDDINGSautooff keeps knowledge base search by words only.
AIGENCY_AUTO_MIGRATEtruefalse stops the automatic database update on the first visit after an upload (then run php artisan migrate --force yourself).
AIGENCY_CA_BUNDLEemptyPath to a CA certificate file, for hosts whose SSL certificate list is too old to reach the AI providers.
AIGENCY_DEMO…offSee Public demo mode.

Public demo mode

To show your site to prospects without risk, turn on demo mode in .env. It is off by default.

SettingDefaultMeaning
AIGENCY_DEMOfalsetrue turns demo mode on.
AIGENCY_DEMO_ADMINemptyE-mail of an existing admin account. The login page shows Sign in as the demo admin (no password). It opens the whole admin, but nothing can be saved there (keys, payments, e-mail, brand, customers) and its password cannot be changed or reset.
AIGENCY_DEMO_CUSTOMERemptyE-mail of an existing customer account. The login page shows Sign in as the demo customer: each visitor gets an account of their own, made on the spot with your welcome credits, so visitors never see each other's chats. The browser keeps it (a cookie) and comes back to it.
AIGENCY_DEMO_VISITORS_PER_IP5New visitor accounts per network per day; past it, the shared demo customer account is used.
AIGENCY_DEMO_ACCOUNTSemptyMore read-only accounts, comma-separated e-mails.
AIGENCY_DEMO_DAILY_MESSAGES20Messages each account may send per day (0 = no limit).
AIGENCY_DEMO_MODELSanthropic.haiku-5-5The only chat models demo users may pick, comma-separated model keys as listed in Admin → Models (empty = all). Other models answer "turned off in the demo".
AIGENCY_DEMO_IMAGESfalseOff: no image is created or charged; the specialist says image creation is turned off in the demo and describes what it would show.

In demo mode the AI voice of "Listen" (the browser voice reads instead) and dictation are also off, and demo accounts cannot open other people's conversations, receipts or knowledge files; e-mail addresses and key endings are masked.

Create the two accounts first: the admin with the installer or an existing admin, the customer by signing up. Then add the lines to .env. Set welcome credits and the preview limits low, and use a provider key with a spending limit: visitors chat with your real AI keys.

Source code and rebuilding

The full source code is included. You only need the steps below if you change the interface (screens, texts in resources/js/, styles); PHP changes need no build.

Path (inside aigency/)What it is
resources/js/Interface source: Vue 3 + TypeScript pages, components and the 14 language files.
resources/css/Tailwind CSS source.
package.json, package-lock.jsonInterface dependencies, locked to the versions we tested.
vite.config.ts, tsconfig.json, tailwind.config.jsBuild configuration.
public/build/The compiled interface the site serves. Shipped unminified and readable.
  1. Install Node.js 20 or 22 (LTS) on your computer.
  2. In the aigency/ folder run npm ci (installs the exact locked versions into node_modules/).
  3. Run npm run build. It replaces public/build/ with a new, minified build (smaller files). For an unminified build, run npm run build -- --mode package instead (the shipped copy was also reformatted for reading; both work the same).
  4. Upload the new public/build/ folder to your hosting. Do not upload node_modules/.

While editing, npm run dev serves the interface with instant reload (needs a local PHP server for the site). Optional checks: npx vue-tsc --noEmit (types) and npm run format (code style).

Updating

  1. Back up the database, the .env file, the storage/ folder and your uploads in public/branding/ (logo) and public/assistants/custom/ (specialist photos you uploaded).
  2. Upload the new files over the old ones, keeping .env, storage/ and those two folders.
  3. If you added an AddHandler line to .htaccess (see Shared hosting notes), add it again.
  4. Open the site. The first visit applies the database updates of the new version automatically (no SSH needed). With SSH you can run them yourself: php artisan migrate --force.
  5. If the version brings new specialist texts, Admin → Areas → Update texts applies them; new packs appear under Ready-made packs.
  6. Clear the caches (below).

Clearing the cache after an update

The interface files get new names with every version, but a browser, a CDN or the server may still hold the old pages for a while. If something looks broken or unchanged after updating (a blank page, an old screen, a button that does nothing):

  1. Your browser: reload without the cache: Ctrl + F5 (Windows/Linux) or Cmd + Shift + R (Mac). If it persists, clear this site's data (Chrome: the icon left of the address → Site settings → Delete data; Safari: Settings → Privacy → Manage Website Data) or try a private window.
  2. CDN or cache of your host: purge it. Hostinger: hPanel → Websites → your site → Performance → CDN → Flush cache (and LiteSpeed Cache, if on). Cloudflare: Caching → Configuration → Purge Everything.
  3. Server cache (optional, with SSH): php artisan optimize:clear.
  4. Tell your customers the same first step if they report an old screen: one hard reload fixes it.

Troubleshooting

SymptomCause and fix
Answers appear all at once instead of word by wordSomething between PHP and the browser buffers the response (a proxy, a CDN, gzip). The installer tests this. On Cloudflare, make sure the site is not cached; on Nginx use fastcgi_buffering off.
"Server busy" while chattingThe simultaneous answer limit was reached; the chat retries automatically. Raise AIGENCY_MAX_STREAMS only if your plan allows more PHP processes.
Test connection failsCheck the key and the provider account balance. If the error mentions SSL certificates, ask your host to update the CA bundle, or set AIGENCY_CA_BUNDLE to the path of a CA file (see Advanced settings).
Blank page or error 500See the latest file in storage/logs/. Check that storage/ and bootstrap/cache/ are writable.
Payment succeeded but credits did not arriveCheck the webhook in the Stripe dashboard (URL and events) and the signing secret in Admin → Plans & billing → Payments. Stripe retries failed deliveries.

Support

Write to willian@polargames.com.br or use the Support tab of the item page on CodeCanyon. Please include your purchase code, your site address, your PHP version and what you see (a screenshot and the text of the error, or the latest file in storage/logs/).

Security notes

Third-party licenses

Every library, font and image included is listed with its license in the THIRD-PARTY-LICENSES/ folder of the download: php-packages.txt (everything in vendor/), javascript-packages.txt (the packages compiled into public/build/ and the build tools), plus-jakarta-sans-OFL.txt and a README.txt. The PHP and JavaScript libraries are under permissive licenses (MIT, BSD, Apache 2.0, ISC), except:

LibraryLicenseUsed for
smalot/pdfparserGNU LGPL 3.0Reading the text of PDF files
dompdf, php-font-lib, php-svg-libGNU LGPL 2.1 / 2.1+ / 3.0+PDF export of conversations
PHPWordGNU LGPL 3.0Word export
nette/schema, nette/utilsBSD-3-Clause (offered as BSD-3-Clause or GPL; used under BSD-3-Clause)Used by the framework's Markdown library
DOMPurifyApache 2.0 (offered as MPL 2.0 or Apache 2.0)Cleaning Markdown output in the browser

The LGPL libraries ship unmodified in vendor/ with their license files, and you may replace them with other versions through Composer. No GPL-only code ships in the package (the packaging script refuses it).

Icons: Lucide (ISC; the parts that come from Feather are MIT). Font: Plus Jakarta Sans by Tokotype, under the SIL Open Font License 1.1 (resources/fonts/plus-jakarta-sans/OFL.txt). It is served from your own site: no request goes to a font service.

Images: the specialist portraits (public/assistants/specialists) and the site and area images (public/images) were generated with AI for this item and are licensed to you with it. They show no real people.