Atlarix has released version 15.9, a significant update for coding agents that streamlines how developers connect to Claude models. The core value proposition is abstraction: whether a team uses a direct Anthropic API key, routes through Amazon Bedrock, or relies on a custom company gateway, the integration experience is now identical. This update targets the fragmentation that often plagues enterprise AI adoption, where billing and infrastructure choices create distinct technical hurdles for the same underlying model.

One Format, Three Routes

The technical backbone of this update is format compatibility. Anthropic’s Messages API (POST /v1/messages) is the standard, and Amazon Bedrock exposes an endpoint that speaks this same dialect. Many enterprise gateways and proxies have also adopted this format. Atlarix now allows users to add providers that speak either OpenAI’s format or Anthropic’s, with the agent communicating via Anthropic’s own SDK when appropriate. For direct Anthropic API users, the process is straightforward: paste the key in the desktop app, CLI, or VS Code panel, and the key is validated immediately before saving. Requests go directly from the local machine to Anthropic, bypassing Atlarix’s servers for inference.

Bedrock and Gateway Specifics

Connecting via Amazon Bedrock requires a bit more configuration due to AWS’s specific requirements. Users must add a custom provider with the API format set to Anthropic, using the base URL https://bedrock-runtime..amazonaws.com/anthropic/v1. Unlike the direct API, Bedrock does not automatically list available models, so developers must manually input the model ID, such as us.anthropic.claude-haiku-4-5-20251001-v1:0. Additionally, new AWS accounts may need to complete a use-case form in the Bedrock console and wait for AWS to enable access to the latest Claude models. For corporate gateways, the setup mirrors Bedrock: if the proxy serves the /v1/messages endpoint, it can be added as a custom provider with its own base URL and key.

Authentication and Feature Parity

A subtle but critical improvement is the handling of authentication headers. Anthropic’s native API expects an x-api-key header, while Bedrock and many gateways prefer a Bearer token. Atlarix now auto-detects the required method by testing both and remembering the successful one. This eliminates the guesswork for developers. Furthermore, feature parity is maintained across routes: thinking modes, prompt caching, and tool use work consistently. The only notable exception is Anthropic’s server-side web search, which is exclusive to the direct API; Bedrock and gateway users must rely on the agent’s local web search tool instead. Billing remains transparent, with costs attributed directly to the user’s chosen provider, not Atlarix.

Key Takeaways

  • Atlarix 15.9 unifies Claude access for direct API, Amazon Bedrock, and custom gateways under a single configuration interface.
  • The update auto-detects authentication methods, switching between x-api-key and Bearer tokens to reduce setup friction.
  • Bedrock users must manually input model IDs and ensure AWS has enabled access to specific Claude versions.
  • Anthropic’s server-side web search is unavailable for Bedrock and gateway routes, requiring fallback to local tools.

The Bottom Line

Atlarix is effectively killing the 'provider lock-in' narrative for coding agents. By making the transport layer agnostic, they’re letting developers choose their cloud or compliance path without sacrificing agent capabilities. This is how AI tooling should scale: infrastructure-agnostic, format-aware, and boringly reliable.