US Jurisdiction for Cloudflare R2

Edge routing for api.captain.dev: requests now connect at an edge location near the caller and travel a private backbone to Captain, so connection handshakes no longer cross the public internet. Nothing changes in your integration.
Most agent integrations open a fresh connection for each query, and that handshake is where the time went. Median v3 Query time on a fresh connection, 100 samples per city:

Calling from	Before	After	Change
São Paulo	805 ms	590 ms	−27%
Singapore	1,136 ms	692 ms	−39%
Sydney	1,065 ms	661 ms	−38%
Dublin	687 ms	529 ms	−23%
Frankfurt	738 ms	555 ms	−25%
San Francisco	641 ms	516 ms	−20%
Portland	656 ms	551 ms	−16%

Index and sync US-jurisdiction R2 buckets: jurisdiction on the R2 indexing and R2 sync requests now accepts us alongside default (global), eu, and fedramp. Jurisdiction-restricted buckets are only visible through their jurisdiction’s endpoint, so a US-restricted bucket previously could not be reached at all; pass "jurisdiction": "us" and Captain talks to https://<account_id>.us.r2.cloudflarestorage.com. The cloud storage guide lists all four options.

Changelog