Business AI API & Website Chat Widget for Paid Workflows

Choose a server integration or a browser widget

The private API is designed for requests from your own server using a purchase key. It gives an application a documented way to ask for a response from an entitled business text workflow. The website widget provides a smaller browser-facing connection with a public widget identifier and an approved website origin. These are different credentials with different purposes. Never copy a private API key into frontend JavaScript, an embed snippet, a public repository, or a page a visitor can inspect.

Keep the purchased workflow and organization in scope

An organization purchase unlocks everyday chat, proposals, company knowledge, sales, and content. An individual service purchase unlocks that service instead. The API checks the key and the active entitlement on the server; a checkout link or frontend label alone does not grant access. Organization knowledge requests can use the shared document library and return selected source excerpts. Usage requests expose organization request activity without asking the model for another answer. Review the developer documentation for the current request shapes, status codes, and limits before connecting an application.

Use a public widget with deliberate boundaries

Enable a widget from organization settings, choose the text workflow, and provide the exact HTTPS website origin. The generated embed contains a public identifier rather than the private purchase key. Requests from other browser origins are rejected, and public visitors have additional request limits. A widget still shares organization capacity, so choose its audience and content carefully. It is suitable for a scoped text interaction, not a promise that every visitor receives an instant answer or that a generated reply constitutes official advice.

Plan for request limits and errors

The $50 USD organization package includes its private API and widget connection tools. Its API allowance is 1,000 requests per minute; individual services allow 60. Actual text generation shares provider capacity, the free daily allocation, and the site’s safety budget. Applications should handle authorization errors, rate limits, and temporary provider failures without retrying indefinitely. Keys are displayed once after purchase and can be rotated or revoked by the owner. Bespoke CRM updates, payment automation, or source synchronization require a separate integration with agreed permissions and review steps.

Evaluate the workflow with your own review checklist

Begin with a sample in the free demo, then compare the draft against its source. Check whether the answer addresses the actual task, preserves important facts, and flags missing information. Decide who will approve the final work and which corrections still require your team. This makes the purchase decision about a practical workflow rather than a promise of automatic results.

Questions before choosing