Fragmented models: switching requires code changes
Each provider has its own SDK, keys, and model list. Switching models requires application changes.
Enterprise AI Implementation
Connect AI to business workflows with governed usage
Enterprise AI implementation connects models with business workflows. The scope includes assessment and consulting before implementation, custom application development and systems integration, and usage governance after launch. Horizon AI's ATP platform connects one project key to more than 16 models, attributes each usage record to a project, and uses prepaid, pay-as-you-go credits with no monthly fee.
PROBLEM｜ Customer challenges
Three risks of connecting to AI models independently
Teams must maintain several connection methods, AI costs do not fit existing allocation processes, keys lack clear boundaries, and routing and resilience must be built separately. These risks may not appear in a demo, but surface after external users enter production.
Fragmented billing: costs cannot enter the allocation process
Token usage and cost for each project are spread across provider consoles and cannot be combined into one report.
Fragmented keys: no clear boundary for access or usage
Scattered keys, unclear permission boundaries, and unlimited usage create risk once external users are involved.
SOLUTION｜ The KONST approach
One system for SDKs, billing, and keys
One project key connects to models from different providers, each usage record is assigned to its project, and permissions are bounded by the key. Implementation proceeds through assessment, custom development, and production governance.
One SDK: one key for models from multiple providers
Compatible with leading provider SDKs, so most applications need only configuration changes.
One bill: assign each usage record to a project
Token usage and costs from every project appear in one report that can feed directly into cost allocation.
One key layer: permissions bounded by each key
Each key can call only authorized models, with its own usage limit and permission scope.
EVIDENCE｜ Results and data
Model access, metering, and governance through one entry point
Providers each maintain their own SDKs, model lists, and billing consoles. ATP connects one key to more than 80 models and brings access, metering, and governance into one entry point.
80+models
Available on the platform, with more being added
1key
One entry point for each project
0monthly fee
Prepaid credits, charged as used
base_url
Compatible with leading SDKs through a configuration change
PROCESS｜ Process
One key from model access through Agent deployment
Trigger an event, select a model, call tools, validate and retry results, then deploy an external-facing Agent. Every step uses the same metering and governance, so background Agent usage is visible.
Trigger event
Identify workflow stages that a model can handle, confirm that the data is available, and then choose an implementation approach.
Select model and provider
The routing layer selects among upstream providers based on availability and cost.
Call tools and execute
Call external tools and internal systems as defined by the workflow, collecting results step by step.
Validate results and retry
Check the output against validation criteria. If it fails, retry by rule or send it for human review.
Deploy as an Agent
After validation, deploy the workflow as an external-facing Agent. Usage and cost remain under the same governance.
PRICE｜ Pricing and fees
Prepaid credits charged as used
Credits are deducted from input and output token counts at each model's rate. Usage is visible in real time and assigned to a project. There is no monthly fee, and annual terms are available for higher volumes.
| Item | Details |
|---|---|
| Billing | Input and output token counts multiplied by each model's rate, then deducted from credits |
| Payment | Prepaid, charged as used, with no monthly fee and no credit expiration |
| Visibility | Real-time usage and cost, attributable to projects |
| High volume | Enterprises with higher usage can discuss capacity and annual terms |
Questions about assessment, access, billing, and governance
What is the first step in enterprise AI implementation?
Start with the workflow, not the model. Look for a stage with clear inputs and outputs, available data, and verifiable results. It is a good starting point only when all three are present. With one model gateway, models can be changed at any time; redesigning a workflow is much more expensive.
How much code must change when moving an existing application to the platform?
The interface is compatible with leading provider SDKs, so most applications need only a new base_url and key. The platform sits behind existing call patterns and does not require a new protocol.
How can usage costs be allocated to departments?
Every call records token counts and deducted credits against a project, workspace, and organization. Credits are allocated from the top down, while usage rolls up from the bottom. Department costs come directly from the platform without separate estimates.
How does platform billing work?
The platform uses credits. Input and output token counts are multiplied by each model's rate and deducted from prepaid credits. There is no monthly fee, and credits do not expire. Enterprises with higher usage can discuss a volume plan.
Will calls stop if one provider has an outage?
The routing layer can switch among upstream providers. If one source fails, another takes over automatically without manual switching.
Does implementation always require a fully custom system?
No. After assessment, the organization can choose an existing application, custom development, or a combination. The integration scope depends on the current information architecture.
Which ready-made enterprise AI applications does KONST Group provide?
Horizon AI currently supports four application categories: enterprise knowledge bases, real-time multilingual AI meeting translation, document AI, and AI factory digital twins. Custom development is also available for industry requirements.
Ready to connect AI to a real business workflow?
Start with a workflow assessment and plan the implementation path for your organization.