Skip to main content

AI Providers

FunnelStory ships with built-in LLM usage for product features such as Renari, Agents, embeddings, and other AI-assisted workflows—so most teams can use those capabilities without touching this screen.

Bring your own LLM (BYO LLM) is for organizations that want AI traffic to run through their preferred vendor and models instead: your own API keys or cloud credentials, your commercial terms with that vendor, and (where supported) your choice of model names and regions. AI Providers under Configure is where workspace administrators register those vendors and wire them into FunnelStory. If you never add a provider, the product keeps using its default LLM path for your workspace (subject to your plan and agreement).

Access requires an Admin, Data Admin, or Super Admin role.

Providers tab​

Use Providers to add and maintain your vendor connections when you are on BYO LLM. Skip this tab if you are not planning to route traffic to a third-party bill you control.

  1. Go to Configure → AI Providers.
  2. Open the Providers tab.
  3. Choose Add Provider and pick a vendor:
VendorWhat you supply
OpenAIAPI key for your OpenAI organization
Google GeminiAPI key for Google AI Studio–style access
Google Vertex AIService account JSON key plus project and region (location) that host Vertex
  1. Save the provider. You can add multiple providers (for example, OpenAI for chat-quality models and Vertex for embeddings) and edit credentials later when keys rotate.

Keep keys in your vault rotation policy: updating a key here is immediate for new AI requests.

Custom Model tab​

When you use BYO LLM, open the Custom Model tab after at least one provider is saved. There you map which of your models FunnelStory should call for each class of work:

  • Large — higher-capability model for complex reasoning or long outputs.
  • Small — faster, cheaper model for structured tasks and high volume.
  • Embedding — model used to vectorize text for search and similarity.

Each slot is a provider + model name pair chosen from the lists supported in the UI for that provider. If you have not completed a custom mapping, the UI may indicate that FunnelStory’s default models are still in use for some workloads—once you save mappings for the slots you care about, eligible features use your vendor for those calls.

Changing mappings applies to new AI runs; in-flight jobs finish on the configuration they started with.

Operational notes​

  • Why BYO: Common reasons include enterprise procurement (single LLM vendor), data residency, existing spend commits, or security review requirements for a specific provider.
  • Credential scope: API keys and service accounts should be least-privilege—only the model endpoints FunnelStory needs.
  • Data residency: For BYO LLM, your provider’s region and data policy apply to prompts and completions sent to that vendor; pick providers and regions that match your compliance requirements.
  • Audit trail: Creating, updating, or deleting providers and editing the custom model map generates entries in the Audit log.