BYOK: bring your own AI API keys to your PIM

BYOK — Bring Your Own Key. Behind this acronym lies an architectural choice that fundamentally changes the relationship between your PIM and AI costs. Here’s why bringing your own API keys is often the best decision, and when managed credits make sense.

The traditional model: credits sold by the provider

Many SaaS tools that incorporate AI operate on a proprietary credit model: you purchase a pack of “AI credits” from the publisher; each data enrichment consumes a certain number; and when you run out, you top up.

This model has several drawbacks for resellers handling large volumes:

• Opaque costs— you don’t know exactly which underlying API call corresponds to which credit
• Publisher’s margin— credits are systematically more expensive than direct API calls; the publisher takes its cut
• Vendor lock-in— you are tied to the AI provider chosen by the publisher, with no option to switch if a competitor becomes cheaper or more efficient
• Privacy— your product data passes through the publisher’s infrastructure before reaching the LLM

The BYOK model: your keys, your bill, your choice

With the BYOK model, you create your own account with OpenAI (or Anthropic, or Gemini, or Mistral…), obtain an API key, and configure it in your PIM. AI calls are billed directly to your account, at each provider’s public rates.

Benefits:

• Total transparency— you can see exactly how much each enhancement costs, in your OpenAI/Anthropic dashboard
• Optimal cost— you pay the published rate, with no publisher mark-up. For large volumes, the difference is significant
• Freedom of choice— you can switch models at any time, or use different models depending on the task (a fast, cheaper model for simple enhancements, a premium model for complex records)
• Controlled privacy— you control which data goes to which provider, and you can configure Ollama for 100% local processing

Cost comparison: a practical example

To enrich 10,000 product records (generating a description + title + 5 attributes):

*Estimates based on average volumes. Actual costs depend on the length of the files and the configured prompts.

Provider Assignments: the right model for every task

ProductsManager allows you to configure a different provider depending on the usage context:

• Batch enrichment— GPT-4o mini or Mistral Small (fast, cost-effective)
• AI Copilot— GPT-4o or Claude (complex reasoning)
• Translation— DeepL (superior quality to general-purpose LLMs for translation)
• Vision / AI Tagging— GPT-4o or Claude (multimodal models)
• Compliance extraction— Claude or GPT-4o (analysis of long documents)
• Self-hosted confidential— Ollama with Llama 3 or Mistral (sensitive data, no cloud)

This granularity allows us to optimise the cost-quality ratio for each use case, rather than using the same (often the most expensive) model for everything.

When managed credits make sense

The BYOK model isn’t always the right choice. Managed credits (available in Growth+) are preferable if:

• You do not wish to manage an account with an AI provider (billing, rate limits, monitoring)
• Your volume is low and the operational simplification is worth the marginal extra cost
• You are in a testing phase and do not wish to commit to a provider before validating the results

Growth+ plans include a monthly quota of managed AI credits for these use cases, in addition to BYOK. You can combine the two: managed credits for everyday use, your own keys for high volumes.

How to set up your first BYOK key

1. Create an account on platform.openai.com (or your preferred provider)
2. Generate an API key in your account settings
3. In ProductsManager, go to AI Services → Providers → Add a provider
4. Select OpenAI, paste your key, and test the connection
5. In Provider Assignments, assign this provider to the desired contexts (enrichment, copilot…)

Setup takes less than 5 minutes and you can run your first enrichment batch immediately.