diff --git a/snapshots/anthropic/api-pricing.md b/snapshots/anthropic/api-pricing.md
index 0bb88a8..961fa86 100644
--- a/snapshots/anthropic/api-pricing.md
+++ b/snapshots/anthropic/api-pricing.md
@@ -33,5 +33,4 @@ The following table shows pricing for all Claude models:
 | Claude Sonnet 4 | $3 / MTok | $15 / MTok | $3.75 / MTok | $6 / MTok | $0.30 / MTok |
 | Claude Haiku 4.5 | $1 / MTok | $5 / MTok | $1.25 / MTok | $2 / MTok | $0.10 / MTok |
-| Claude Haiku 3.5 | $0.80 / MTok | $4 / MTok | $1 / MTok | $1.60 / MTok | $0.08 / MTok |
 
 Additional notes
@@ -45,5 +44,5 @@ Claude 4.7 and later models and Claude Mythos Preview use a newer tokenizer that
 This section covers partner-operated cloud platforms, where the cloud provider invoices you. For Anthropic-operated cloud platforms billed through a marketplace, see Claude Platform on AWS pricing, Claude Models on Google Cloud (Anthropic managed) billing, and Claude in Microsoft Foundry pricing.
 
-Claude models are available on Amazon Bedrock and Claude Models on Google Cloud (Google managed). For official pricing, visit:
+For official pricing on Claude Models on Google Cloud (Google managed) and Amazon Bedrock, visit:
 
 - Amazon Bedrock pricing
@@ -139,5 +138,5 @@ For implementation details, supported models, and code examples, see Prompt cach
 For Claude 4.6 and later models, specifying US-only inference through the `inference_geo` parameter incurs a 1.1x multiplier on all token pricing categories, including input tokens, output tokens, cache writes, and cache reads. On Claude Haiku 5.5, the multiplier also applies to the higher prices for prompts over 100,000 tokens (see Long context pricing). Global routing (the default) uses standard pricing.
 
-This applies to the Claude API (first-party), Claude Platform on AWS, and Claude Models on Google Cloud (Anthropic managed). On Claude in Microsoft Foundry, the same 1.1x multiplier applies to deployments that use the US Data Zone Standard deployment type (see Inference geography). Partner-operated platforms, Bedrock and Claude Models on Google Cloud (Google managed), have independent regional pricing. See Bedrock pricing and Google Cloud pricing for details. Earlier models do not support the `inference_geo` parameter and always use standard pricing; requests that include the parameter on these models return a 400 error.
+This applies to the Claude API (first-party), Claude Platform on AWS, and Claude Models on Google Cloud (Anthropic managed). On Claude in Microsoft Foundry, the same 1.1x multiplier applies to deployments that use the US Data Zone Standard deployment type (see Inference geography). Partner-operated platforms, Claude Models on Google Cloud (Google managed) and Bedrock, have independent regional pricing. See Bedrock pricing and Google Cloud pricing for details. Earlier models do not support the `inference_geo` parameter and always use standard pricing; requests that include the parameter on these models return a 400 error.
 
 For more information, see Data residency.
@@ -189,5 +188,4 @@ The Batch API allows asynchronous processing of large volumes of requests with a
 | Claude Sonnet 4 | $1.50 / MTok | $7.50 / MTok |
 | Claude Haiku 4.5 | $0.50 / MTok | $2.50 / MTok |
-| Claude Haiku 3.5 | $0.40 / MTok | $2 / MTok |
 
 For more information about batch processing, see Batch processing.
@@ -249,6 +247,4 @@ When you use `tools`, the API also automatically includes a special system promp
 | Claude Haiku 4.5 | `auto`, `none` | 496 tokens |
 | `any`, `tool` | 588 tokens |  |
-| Claude Haiku 3.5 | `auto`, `none` | 264 tokens |
-| `any`, `tool` | 355 tokens |  |
 
 These token counts are added to your normal input and output tokens to calculate the total cost of a request.
@@ -335,5 +331,5 @@ Web search usage is charged in addition to token usage:
 Web search is available on the Claude API for $10 USD per 1,000 searches, plus standard token costs for search-generated content. Web search results retrieved throughout a conversation are counted as input tokens, in search iterations run during a single turn and in subsequent conversation turns.
 
-Each web search counts as one use, regardless of the number of results returned. If an error occurs during web search, the web search will not be billed.
+Each web search counts as one use, regardless of the number of results returned. A web search that fails with an error is not billed.
 
 #### Web fetch tool