claude-on-vertex-ai changedbuild-with-claude/claude-on-vertex-ai
Nearest release: v2.1.307, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+7added
Lines−7removed
From line
390
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits38to this page, all time
The whole hunk
from line 390, old and new numbered
/
from line 390
390390
391391Claude Fable 5.1, Claude Fable 5, Claude Opus 5.5, Claude Opus 5, Claude Opus 4.8, Claude Opus 4.7, Claude Opus 4.6, Claude Sonnet 5.5, Claude Sonnet 5, Claude Sonnet 4.6, and Claude Haiku 5.5 have a [1M-token context window](https://platform.claude.com/docs/en/build-with-claude/context-windows) on Agent Platform. Other Claude models, including Sonnet 4.5 (deprecated) and Sonnet 4 (deprecated), have a 200k-token context window.
392392
393Agent Platform limits request payloads to 30 MB. When sending large documents or many images, you might reach this limit before the token limit.
393Agent Platform limits request payloads to 30 MB. When sending large documents or many images, you might reach this limit before the token limit.
394394
395395## Global, multi-region, and regional endpoints
396396
from line 400
400400* **Multi-region endpoints:** Dynamic routing within a geographic area (for example, the United States or the European Union) for data residency with high availability
401401* **Regional endpoints:** Guaranteed data routing through specific geographic regions
402402
403Regional and multi-region endpoints include a 10% pricing premium over global endpoints.
403Regional and multi-region endpoints include a 10 percent pricing premium over global endpoints.
404404
405405<Note>
406406 This applies to Claude Sonnet 4.5 (deprecated) and future models only. Older models (Claude Sonnet 4 (deprecated), Opus 4 (deprecated), and earlier) maintain their existing pricing structures.
from line 412
412412
413413* Provide maximum availability and uptime
414414* Dynamically route requests to regions with available capacity
415* No pricing premium
416* Best for applications where data residency is flexible
417* Only supports pay-as-you-go traffic (provisioned throughput requires regional endpoints)
415* Carry no pricing premium
416* Work best for applications where data residency is flexible
417* Only support pay-as-you-go traffic (provisioned throughput requires regional endpoints)
418418
419419**Multi-region endpoints:**
420420
421421* Dynamically route requests across regions within a geographic area (currently `us` and `eu`)
422422* Useful when you need data residency within a broad geography but want higher availability than a single region
423* 10% pricing premium over global endpoints
423* 10 percent pricing premium over global endpoints
424424* Only supports pay-as-you-go traffic (provisioned throughput requires regional endpoints)
425425
426426**Regional endpoints:**
from line 428
428428* Route traffic through specific geographic regions
429429* Required for single-region data residency, strict compliance mandates, or provisioned throughput
430430* Support both pay-as-you-go and provisioned throughput
431* 10% pricing premium reflects infrastructure costs for dedicated regional capacity
431* 10 percent pricing premium reflects infrastructure costs for dedicated regional capacity
432432
433433### Implementation
434434
No line in this hunk matches that.