Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Sign inRegister
Model keys

Bring Your Own LLM Key: Use Your Organisation's Model Accounts Across Apragya

For IT heads and CTOs whose organisation already holds model provider accounts and wants every AI feature to run on them, with keys kept out of sight.

Start freeTalk to sales
A technology head placing a brass key into a lock box

Bring your own LLM key means your organisation's AI features run on your own model provider account rather than a shared one. Many companies already have an agreement with a provider, with their own data terms, limits and billing.

The difficulty is handing that key out safely. Keys get pasted into scripts, shared on chat and left in old tools, and nobody knows which app is using which account.

This page covers what loose keys cost, an illustrative example, and how Apragya stores and uses your keys across its AI features.

What scattered model keys cost

Leaked keys

A key pasted into a script or chat ends up where it should not.

No visibility

Nobody can say which tool used the key or how much.

Painful rotation

Changing a key means hunting through every tool that holds it.

Data terms ignored

Staff use personal accounts that lack your agreed terms.

An example: a Hyderabad IT services firm

Take an illustrative 120-person firm with an enterprise agreement with a model provider, including its own data handling terms. The CTO wanted every AI feature in Apragya to use that account and no other.

The key record, as the admin sees it

Organisation model key

  1. One key per provider for the organisation.

  2. The full key is never shown again.

  3. Enough to tell keys apart.

  4. A wrong key is caught straight away.

  5. Used before any platform key.

  6. Every feature picks up the new key.

One record replaced a key that had lived in five different tools.

After the key was added, chat, document reading and agents all ran on the firm's own account. When the security team rotated the key three months later, the admin replaced it once and nothing broke.

A key board with hooks and one key on a single hook
One key in one place, replaced once when it was rotated.

How LLM API key management works in Apragya

Step 1 of 5

Add the key

An admin adds a key for a supported provider.

  1. Add the key: An admin adds a key for a supported provider.
  2. Encrypt it: The key is encrypted at rest and only a short hint is ever shown.
  3. Test it: A live check confirms the key works when it is saved.
  4. Resolve it: Each AI call uses the organisation key first, then a personal key, then the platform key.
  5. Offer models: Model pickers show only models that have a usable key.

BYOK AI in India: what to check

Supported providers include Anthropic, OpenAI, Google, Mistral and Groq. Some providers route data through third parties or other countries, so those need an explicit opt-in by the organisation before a key can be stored. That matters for firms with client data commitments.

Keys in scripts against Apragya key management

FeatureKeys in scripts and toolsApragya organisation keys
StoragePlain text in filesEncrypted at rest
VisibilityFull key copied aroundOnly the last characters shown
CheckingFails at run timeTested when saved
RotationEvery tool updatedReplaced once
Usage recordScatteredLogged and labelled by key source

Checked against public information on 16 September 2026.

What sets Apragya apart when you use your own OpenAI key or another provider

One key, every feature

Chat, writing, agents and app building use the same resolution.

Personal keys too

Users can add their own keys where allowed.

Opt-in for some providers

Providers with other data routes need explicit approval.

Usage by source

Reports show which calls ran on your key.

Admin only

Who can add or change keys is set by role.

Metered view

Usage is still recorded in AI Credits terms for reporting.

Read how AI Credits are metered, or see how the AI chat assistant uses your models. For stricter setups, see on-premise AI.

Getting started

  1. Check your provider agreement and data terms.
  2. Create a key meant only for Apragya.
  3. Add it as the organisation key and let the live test run.
  4. Tell staff to stop using personal accounts for work.
  5. Put the key's rotation date in the security calendar.

A key created only for Apragya is easy to rotate and easy to revoke.

What it costs to start

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

Bring your own key questions

Can we see the key after saving it?
No. Only the last few characters are shown. To change it, replace it.
Which providers are supported?
Anthropic, OpenAI, Google, Mistral and Groq, with some others available after an explicit opt-in.
Is usage on our key still recorded?
Yes. Calls are logged and labelled with the key source. Ask our team how it counts for your plan.
What if our key stops working?
Replace or remove it. Without an organisation key, calls use the next key in order, where one is configured.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

Run Apragya's AI on your own account

Add one organisation key, let it test, and every AI feature will use it.

Start freeTalk to sales