Anthropic SDK (TypeScript) vs OpenRouter
Side-by-side trajectory, velocity, and editorial themes.
Anthropic ships a dedicated AWS client for Claude Platform on AWS, alongside steady Managed Agents expansion.
The TypeScript SDK family is on a weekly bump cadence (0.94 → 0.97 in two weeks) with two structural moves underneath. First, a new [email protected] introduces an AWS client for Claude Platform on AWS — a distinct package from the existing bedrock-sdk. Second, Managed Agents (CMA) is broadening visibly: webhooks, multiagents and outcomes types, vault validation, self-hosted sandboxes with helpers, a BetaManagedAgentsSearchResultBlock, and cache diagnostics beta in successive releases.
Anthropic is splitting its AWS distribution into two channels — Bedrock for the model API, and a separate Claude Platform on AWS surface that the new aws-sdk implies will bundle Managed Agents and related platform features. Managed Agents itself is hardening from a single-agent harness into a multi-agent orchestration product with webhooks, outcomes, and self-hosted execution. The combination reads as Anthropic moving from model API to deployable agent platform.
Expect a public Claude Platform on AWS announcement (likely an AWS Marketplace listing or product page) once [email protected] stabilizes. Managed Agents will keep adding orchestration surface — likely persistent memory hooks, audit endpoints, or agent-to-agent messaging primitives.
OpenRouter is becoming a full agent platform, not just a model router.
OpenRouter has rolled out an Agent SDK, universal web search and fetch for any tool-calling model, dedicated audio APIs for TTS and transcription, and a response cache that drops cost to zero on repeat requests. It is also publishing pricing analyses that benchmark frontier-model cost shifts. The April-30 'release spotlight' frames the past month as a multi-product push rather than incremental shipping.
The product is moving up the stack from per-token model routing toward an opinionated developer surface — tool use, caching, multi-modality, account provisioning via CLI — so that an agent built on OpenRouter does not need separate vendors for search, audio, or workflow scaffolding. The Stripe-driven CLI signup hints that agents themselves are now an addressable customer.
Next likely move is expanding the Agent SDK with shared evaluation and traces across providers, plus deeper caching primitives — turning model-routing economics into a real switching argument against single-provider SDKs.
See more alternatives to Anthropic SDK (TypeScript) →
See more alternatives to OpenRouter →