Designs, builds and tests the workflow
- Designs the workflow with your team
- Connects your data and the models
- Sets who can send which data to which model, and when to switch models
- Tests results on your own cases
- Helps you run and monitor it
We test it on your own past cases before a production build. If it meets your quality, cost and data requirements, we build it into your workflow. If it does not, you have the evidence to keep your current approach.
Works with the inference provider you choose, a frontier API, or your own cloud. You hold the accounts and the bills.
Agree what good looks like and which failures are unacceptable.
Your current frontier model, an open model as it is, and a tuned model only where the numbers justify it.
Connect the real data sources and the chosen models for that one workflow.
Quality, cost per 1,000 cases, speed and critical failures for each option, with a recommendation: scale it, change it or stop.
What you get: a written report, the tested set of cases, the working limited integration, and a signed passport for any model we recommend. Scope is agreed with you up front.
Rules by role and by type of data. For example, customer records go only to models inside your cloud.
In your cloud, with a UK or EU provider on GPUs or specialised inference hardware, or through a frontier API. We check residency, contractual controls and model support for the chosen route.
Cost per 1,000 cases for each model, measured in testing and tracked once it runs.
We re-run your locked test set whenever a model or its version changes, and each approved version carries a signed passport.
Routing tools pick a model for each request. We give you the tested rules and the evidence behind them, across the whole workflow.
In a pilot: your own sign-in, four roles, an audit trail, signed jobs, a locked test set, and containers that run in your cloud.
Bring your model, expected usage and data rules. We help you compare hosting routes, then connect the chosen service to your workflow.
Model and licence, data location, throughput, response time, security and support. UK or EU hosting is assessed alongside the contract and operational controls.
Check GPU or specialised inference hardware, support for your model weights, capacity and total operating cost. Availability and compatibility are confirmed with the provider.
You choose the provider and contract with them directly. You hold the account and the hosting bill; AgenTek scopes its advice and integration separately.
If a provider pays AgenTek a referral fee, we disclose it before you decide.
AgenTek is a senior-led UK consultancy. Chandra brings architecture experience across AI, data platforms, cloud and identity, including work in regulated sectors.
He works with your team on the business case, evaluation, integration and handover. Specialist delivery support is agreed with you as part of the scope.
We are looking for referral and co-sell relationships with providers serving UK and EU customers.
ModelFit is the tool we use to test each option on cases it has never seen. The test set is locked before any model is tried, and each approved model gets a signed passport your risk team can check.
OpenAI ends new self-serve fine-tuning jobs for active existing customers on 6 January 2027. Listed GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini snapshots, including their fine-tunes, retire on 14 January 2027. Check the affected models and dates. We can test a replacement API or an open model against your own cases before you switch.