Applies to:
- Plan - Enterprise
- Deployment - Hybrid, BYOC
- Data plane - v2.0 or later
- Use case - AI provider calls fail after a data plane v2 migration because provider authentication or endpoint path metadata needs to be updated
Summary
After upgrading to data plane v2, AI provider configurations can fail ifauth_format or endpoint_path metadata no longer matches the upstream provider. Data plane v2 respects auth_format when forwarding provider credentials and treats serialized endpoint_path: "" values differently, so affected providers need to be recreated or updated.
Symptoms
Model calls through Braintrust fail after upgrading to data plane v2, even though the same provider credentials worked before the upgrade. This issue usually affects provider configurations that include one or both of these metadata fields:auth_formatset to a value other thanbearer.endpoint_path: ""in the Raw configuration.
Cause
Before data plane v2, Braintrust ignoredauth_format in some provider configurations and sent provider credentials using Bearer authentication. Data plane v2 respects auth_format, so a provider configured with auth_format: api_key sends the credential as an API key instead of a Bearer token.
Some provider configurations saved before March 17, 2026 serialized endpoint_path: "" into the configuration metadata. Remove endpoint_path from the Raw configuration, or recreate the provider, to prevent the empty value from affecting provider routing.
Resolution steps
Step 1: Check the provider auth_format
Go to Settings > AI providers. Open the affected provider’s Setup tab, expand More settings if it is collapsed, and select Raw to inspect the configuration.
If auth_format is set to a value other than bearer and the upstream provider expects Bearer authentication, recreate the provider with the correct auth_format.
Step 2: Remove an empty endpoint_path
If the provider configuration includes endpoint_path: "", delete endpoint_path from the Raw configuration and click Update. If you cannot remove the field from the existing configuration, recreate the provider instead.