/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Anthropic releases “tool use” for Claude, letting users create AI assistants, available via Anthropic's Messages API, Amazon Bedrock, and Google's Vertex AI

The Verge Kylie Robison

Context & Ripple Effects

This is an early platform-distribution move: Claude capabilities are exposed through Anthropic’s own API while also reaching developers on Amazon Bedrock and Google Vertex AI. That makes assistant-building a deployment concern across cloud model platforms, not only a feature of Claude’s direct interface.

The subsequent product arc expands the same premise from tool invocation to visible, interactive outputs in Claude Artifacts and later to a developer-focused managed-agent deployment layer.

First-order effects

  • Developers can build Claude-based assistants that use tools, with access through the Messages API as well as Bedrock and Vertex AI.
  • Anthropic gains distribution inside two major cloud AI environments, while their customers get another model option for assistant workflows.

Second-order effects

  • Cloud-platform users can evaluate Claude tool use without adopting Anthropic’s API directly, increasing pressure on model platforms to compete on integration breadth and developer experience.
  • The feature creates a foundation for Claude to move beyond chat responses toward task-oriented workflows, later reflected in code execution and file analysis capabilities.

Third-order effects

  • If tool access becomes a standard model-layer capability, differentiation will shift toward the reliability, controls, deployment tooling, and workflow surfaces surrounding agents rather than raw chat alone.
  • Cross-cloud availability can make the agent stack more modular: model providers, cloud hosts, and application builders may increasingly compete for different layers of the same assistant workflow.

The trend: Foundation-model vendors are turning conversational models into deployable agent components that can act through tools across cloud platforms.

Discussion

  • @anthropicai @anthropicai on x
    Tool use is now generally available. With tool use, Claude can, if instructed, intelligently select and orchestrate tools to solve complex tasks end-to-end. Start building today with our API, Amazon Bedrock, or Google Vertex AI: https://anthropic.com/...
  • @minimaxir Max Woolf on x
    Message streaming with tool use/structured data is *interesting*. I wonder if there's an easy way to parse the returned JSON in real time.
  • @alexalbert__ Alex Albert on x
    Tool use for Claude is now generally available in our API, Amazon Bedrock, and Google Vertex AI. With tool use, you can easily build powerful agent workflows using Claude. Here are 5 agent + tool use architectures I've seen working in the wild🧵 https://x.com/...
  • @anthropicai @anthropicai on x
    Early customers use Claude with tool use to build bespoke experiences—@StudyFetch uses Claude to power Spark.E, a personalized AI tutor that helps students study more effectively. [image]
  • @anthropicai @anthropicai on x
    Tool use also supports message streaming, “forced” tool choice, and vision support—helping you build more natural, focused, and multimodal experiences. https://x.com/...