Supplemental Terms for RegiaBI Programmatic Access

Supplemental Terms for the RegiaBI API and MCP Server

Revised: August 9, 2026

These supplemental terms ("RegiaBI Terms") apply to your use of the RegiaBI charting engine through any interface OTHER than a CodeX-published end-user client — including our HTTP API, our Model Context Protocol (MCP) server, and any SDK or command-line tool we publish for that purpose (together, "Programmatic Access"). They are made available by CodeX Enterprises LLC ("CodeX", "we", "us", "our") (doing business as "BI-Champ", "RegiaBI", "bizintelligencechampions.com" and "Biz Intelligence Champions"). They are IN ADDITION TO and form part of our general Terms of Use & Privacy Policy at https://bizintelligencechampions.com/terms. Where these supplemental terms address a topic differently than the general Terms, these supplemental terms control with respect to Programmatic Access.

Your use of Programmatic Access constitutes acceptance of these terms. If you do not agree, you must not use Programmatic Access.

1. SCOPE, AND WHAT IS COVERED ELSEWHERE

a. What these terms cover. Any call your software makes to our backend that is not made by a CodeX-published end-user client. This includes chart generation, data-shape assessment performed server-side, and chart-type eligibility (the "what fits this data" call), whether or not the particular call consumes usage credits.

b. What these terms do not cover. Use of the "LLM AI Charts" Power BI visual is governed by the LLM AI Charts Terms, and use of any CodeX-published Office or spreadsheet add-in is governed by those same terms as applied to that client. Use of the website and your Account is governed by the general Terms of Use. Our separately-published open-source packages are governed by the license distributed with each package, and nothing in these terms narrows a right granted by such a license.

c. Incorporated by reference. Sections 3 (data sent to LLM providers), 4 (data we log on our servers), 5 (code generated), 6 (cost and credits), 7 (availability, rate limiting, and changes), 9 (suspension and termination), and 10 (disclaimers, liability, and indemnity) of the LLM AI Charts Terms apply to Programmatic Access, reading "the Visual" as "Programmatic Access" and "your report" as "your calling application". They are not restated here so that the two documents cannot drift apart.

2. LICENSE REQUIRED

a. Programmatic Access requires an active license on your Account. There is no freemium tier for Programmatic Access, and the evaluation allowance that exists inside our end-user clients does not extend to it.

b. The eligibility call is licensed, and metered beyond a free allowance. The "what fits this data" call includes a free allowance of calls per rolling hour, per Account; calls beyond the allowance consume usage credits from your Account at a per-call rate. Both the allowance and the rate are configuration-driven and may change at any time without notice; a call that would be charged when your Account holds insufficient credits is refused with a message saying so, never silently dropped or billed into a negative balance. The call requires an active license even within the free allowance, because the answer it returns is the output of the engine itself rather than a byproduct of generating a chart.

c. Credentials are per-Account and are yours to protect. Your licensee name, license key and (where configured) Client Secret Key authenticate calls billed to your Account. Do not embed them in client-side code, public repositories, container images, or anything you distribute. Section 10 of the LLM AI Charts Terms applies to loss arising from exposed credentials.

d. One Account, one organization. A license entitles the licensed organization and its personnel to make calls. It does not entitle you to make calls on behalf of a third party, to resell access, or to operate a shared endpoint through which unlicensed parties reach the engine. If you want to embed RegiaBI in something you distribute, contact us — that is a conversation we are happy to have, and it is not this license.

3. YOUR DATA, AND YOUR RESPONSIBILITY FOR IT

a. You are the one choosing what to send. Programmatic Access has no user interface between your data and our backend. Column names, data profiles, sample rows and any prompt text you supply are transmitted as your software sends them, and are handled as described in Sections 3 and 4 of the LLM AI Charts Terms — including onward transmission to a third-party LLM provider for generation calls.

b. The prohibited-data restrictions apply unchanged. The restrictions in Section 8 of the LLM AI Charts Terms — HIPAA-regulated data, PCI DSS cardholder data, GDPR Article 9 special categories, classified or export-controlled data — apply in full. An automated caller makes it materially easier to send such data by accident, and that risk sits with you.

c. Automated callers and agent frameworks. Where your calling application is an autonomous agent or is otherwise driven by a language model, you remain responsible for what it sends and for the volume it sends. We are not liable for credit consumption, data transmission, or generated content arising from an agent operating on your credentials.

4. PROHIBITED USES SPECIFIC TO PROGRAMMATIC ACCESS

In addition to the prohibited uses in Section 2 of the general Terms and Section 8 of the LLM AI Charts Terms, you may not:

Systematically enumerate, mirror, cache for redistribution, or otherwise bulk-extract our chart catalog, chart ontology, eligibility rules, prompt corpus, code-quality rules, or the eligibility engine's outputs across synthetic or exhaustive inputs. Calling the eligibility endpoint for datasets you are actually working with is exactly what it is for; sweeping it to reconstruct the rules behind it is not.
Use Programmatic Access, or anything derived from its outputs, to train, fine-tune, distil, evaluate against, or otherwise develop a service that competes with RegiaBI.
Present RegiaBI output as the product of your own engine, or otherwise misrepresent the origin of generated charts, in a product you distribute or sell.
Circumvent, or attempt to circumvent, the license check on any endpoint — including by misreporting your client or host identity in a request.
Operate Programmatic Access at a request rate that degrades service for other customers, or retry a failing call in an unbounded loop.

5. STABILITY OF THE INTERFACE

a. Programmatic Access is evolving and is not versioned as a stable contract. Request and response shapes, field names, chart-type names, eligibility outcomes, ranking, and the set of available endpoints may change at any time without notice. Write your caller defensively: tolerate unknown fields, do not assume a chart type will remain eligible for a given shape, and do not depend on ranking order being stable between calls.

b. Eligibility answers are not advice. That a chart type is reported eligible means it can be drawn from the shape you described. It is not a statement that the chart is appropriate for your analytical question, nor that any conclusion drawn from it is correct. Section 10 of the LLM AI Charts Terms applies.

6. REVISIONS TO THESE TERMS

We may revise these RegiaBI Terms at any time by posting an updated version at https://bizintelligencechampions.com/terms-regiabi. Revisions are effective when posted. Where the change is material, we will use commercially reasonable effort to notify Accounts via the email on file. Your continued use of Programmatic Access after revisions take effect constitutes acceptance.

7. CONFLICT

To the extent there is a conflict between these RegiaBI Terms and the LLM AI Charts Terms, these RegiaBI Terms control with respect to Programmatic Access, and the LLM AI Charts Terms control with respect to the Visual. To the extent there is a conflict between either and the general Terms of Use, the supplemental terms control within their own scope. All other provisions of the general Terms continue to apply.