# AI model provider selection

Provider selection connects AI features to the model service that processes their requests.

*Release 3.3 · developer*

**Settings › AI › Models** · **Settings › AI › Accounts**

## What it is

A **Provider** connects an AI feature to a model service. INSIDE translates the feature's conversation, instructions and available tools for that service, then reads the reply. This lets different model services be used without rewriting the feature's business instructions.

## Who uses it and why

Developers agree service compatibility and integration requirements with Powerfront. Powerfront configures the provider through the website's models and AI accounts.

## Where to find it

**Provider** appears in the model editor at **Settings › AI › Models**. Accounts use those models at **Settings › AI › Accounts**. Powerfront manages both screens for you.

## How it works

1. An AI feature uses its selected account.
2. An **AiFlow** account uses the provider associated with its selected model, or the configured gateway route.
3. INSIDE passes the instructions and conversation to that service. Where supported, the request also includes images, documents, tool history or a required reply format.
4. The service returns reply content, tool requests and usage information. INSIDE uses those results to continue the feature's work.

Tool requests and their results remain associated with the conversation. Some services also need private continuation information to preserve their own conversation history. That information is excluded from the public reply representation.

## Configure it

Ask Powerfront to select a provider and model appropriate to your feature. Confirm tool calling, image or document input, structured replies and streaming separately. Support varies by provider, model and connection.

Powerfront can arrange a custom provider integration where needed. The standard **Provider** menu lists the built-in choices; a custom integration needs separate configuration by Powerfront.

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Provider | Settings › AI › Models | Yes | Identifies the service to use for this model; new records start with OpenAI. |
| Model | Settings › AI › Accounts | No | Selects the website model whose provider is used by an AiFlow account. |

## Limits and good to know

- An unavailable provider produces an error. Provider selection does not imply automatic failover to another service.
- With the explicit **OpenAI** provider, the default API choice uses **Responses API**. Older configurations without an explicit provider retain the older Chat Completions selection behaviour.
- A provider that returns only a complete reply can still be used. INSIDE can report **Thinking** while waiting, then receive the finished reply.
- Embeddings and realtime voice have separate configuration. Choosing a conversation provider does not configure those services.
- A provider change can affect tool handling and conversation history. Ask Powerfront to check the affected AI features when making the change.

## Depends on and works with

### This feature uses

- **Requires** [AI accounts and shared defaults](AIP-001.md): An AI account supplies the connection used by the feature.
- **Configured in** [AI model catalogue](AIP-002.md): AiFlow uses the provider recorded against the selected website model.
- **Configured in** [Custom scripts managed by Powerfront](EXT-015.md): Powerfront-managed custom scripts can supply an additional provider integration.
- **Works better with** [AI functions and required inputs](AI-016.md): Tool-capable providers can request functions made available to an AI feature.
- **Works better with** [Rich content in AI replies](AI-026.md): Enabled rich replies let compatible providers return structured content for supported AI features.
- **Works better with** [Images and attachments for AI agents](AI-039.md): Supported providers can accept image and document context.
- **Works better with** [OpenAI API connection options](AIP-004.md): OpenAI is an available provider with two API choices.
- **Works better with** [Google AI Studio model connection](AIP-005.md): Google AI Studio supplies another model connection.
- **Works better with** [AWS Bedrock model connection](AIP-006.md): AWS Bedrock supplies another model connection.
- **Works better with** [Cloudflare AI Gateway connection](AIP-007.md): Cloudflare AI Gateway can route supported model requests.
- **Works better with** [Salesforce Models API connection](AIP-027.md): Salesforce Models API is another provider choice.

### Used by

- **Related** [AI model catalogue](AIP-002.md): Review provider compatibility when choosing a model from the website catalogue.

## FAQ and troubleshooting

### Can I change providers by editing the prompt?

No. The account and model connection determine the provider. Ask Powerfront to change that configuration.

### Why does the same feature behave differently with another model service?

Services differ in supported inputs, tool controls and reply formats. Check that the chosen connection supports everything the feature uses.

### Can I install my own provider through Settings?

Powerfront manages provider integrations. Ask Powerfront to arrange the custom integration.

### Does a provider error trigger another provider automatically?

No general provider failover is established for this release. Feature-specific error handling is configured separately.