{"version":"2.1.251","anchor":"bifrost-and-databricks-are-recognized-as-ai-gateways","canonical_anchor":"bifrost-and-databricks-are-recognized-as-ai-gateways","heading":"Bifrost and Databricks are recognized as AI gateways","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/bifrost-and-databricks-are-recognized-as-ai-gateways","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Bifrost and Databricks are recognized as AI gateways\n\nBifrost and Databricks are now recognised as AI gateways in response labelling.\n\n**What**\n\nWhen your API traffic goes through a gateway, Claude Code labels the responses with which gateway it was. It now recognizes Bifrost, by an `x-bifrost-` response header prefix, and Databricks, by hostnames ending in `.cloud.databricks.com`, in addition to litellm, helicone, portkey, cloudflare, kong and braintrust. litellm also now reports its version from a dedicated header.\n\n**Details**\n\n- Detection is passive: headers and hostname only, nothing is sent to the gateway to ask.\n\n**Evidence**\n\n`x-bifrost-`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}