Providers, models and prices
Location: Modelli e policy. Global provider and target management requires a Netter administrator.
Connect a provider
- Open Provider upstream and add a provider.
- Enter name, strategy/type, base URL and required credential.
- Save and check enabled status.
- Create model mappings for the protocols you will expose.
Authentication strategies and generation parameters depend on provider type. Upstream credentials are encrypted and must not be distributed to customers. Test a compatible endpoint using the actual protocol it will receive.
Add a mapping
A mapping connects public name, provider, exact upstream ID and operation:
| Field | Requirement |
|---|---|
| Public name | Name or alias for portal and clients; defaults to the complete upstream ID when omitted |
| Operation | Route protocol and capability: chat, Messages, Responses, embeddings or media |
| Upstream ID and path | Exact provider values, preserving namespaces |
| Capabilities | Only verified tools, vision, structured output and other supported features |
| Input/output limits | Consistent with model, protocol and economic reservation |
| Reasoning effort | Supported levels and approved native parameters |
| Currency and prices | Input, output, cache and applicable media prices |
One public name can have separate mappings for different protocols. Do not simulate an upstream API that is absent or treat an alias as a capability guarantee.
Presets help populate some fields. Verify current availability, prices and terms before enabling a model; a preset is not certification of the remote service.
Prices, cache and exchange rates
Prices use supported sources or verified manual entry. Foreign-currency rates need a valid EUR exchange rate. Expired prices or exchange rates, normally beyond 24 hours, exclude a route until refreshed.
Prices distinguish input, output, cache and applicable media. Charges use measured counters and each request's price/exchange snapshot, with Netter's 1.40 multiplier. Never replace an unknown price source with a zero price.
Provider balance
Customer credit is separate from the Netter upstream account's balance. Customers with positive credit may still receive provider errors if the upstream account is depleted.
Supported periodic balance checks notify Netter administrators of low or unreadable balances. Add upstream credit in that provider's console; this does not top up a customer wallet.
Rename, disable and delegate
Renaming a public model updates configured references while preserving historical usage, upstream IDs and journal entries. Clients using the old name must update model. Saved chats may retain their historical label.
Subordinate mappings keep a reference to the approved target so higher-level revocation propagates. Check effects on Switchyard, Responses contexts and clients before disabling a route.
Continue with Switchyard and policies.