Vectorize on Agent Zone

Cloudflare Search Optimization: A Tiered Methodology (App -> Schema -> Platform)

Wed, 20 May 2026 00:00:00 +0000

Cloudflare Search Optimization: A Tiered Methodology#

A CF Workers + D1 + KV search endpoint has three classes of work you can ship to make it faster. They differ by cost-to-ship, not by impact. Order them right and you ship ~50% latency reduction in a day; order them wrong and you burn a week on Vectorize when the real win was a SELECT * you forgot to trim.

This page is the methodology, observed end-to-end on api.agent-zone.ai/api/v1/knowledge/search going from a 677ms baseline to 355ms then unlocking platform-level scale. Each tier is scope -> moves -> measured impact -> shipped commit.

Cloudflare Vectorize Id 64-Byte Limit: The Hash-with-Metadata-Roundtrip Pattern

Wed, 20 May 2026 00:00:00 +0000

Cloudflare Vectorize Id 64-Byte Limit#

Cloudflare Vectorize caps vector ids at 64 BYTES, not 64 characters. The naive if id.length <= 64 skip-hashing check passes Unicode through and then fails at upsert time. The right pattern is unconditional SHA-256 hex hashing with the original id stored in metadata so query results round-trip back to your source-of-truth row.

TL;DR#

The limit is 64 bytes, not 64 chars. Multibyte UTF-8 hits it sooner than ASCII.
Always hash the id. Never branch on length.
Put the original id in metadata.id. Resolve back at query time.
A single oversized id fails the WHOLE batch — partial-success semantics.

The error#

VECTOR_UPSERT_ERROR (code = 40008): id too long; max is 64 bytes, got 67 bytes

This is a 4xx-class refusal at the upsert API. One bad id in a vectorize.upsert([...]) batch rejects every vector in the call — it is not partial-success-with-warnings. If you batch 100 vectors and one has a 67-byte id, all 100 silently fail to land.

FTS5 vs Cloudflare Vectorize: A/B Results on When Keyword Beats Semantic Search

Wed, 20 May 2026 00:00:00 +0000

FTS5 vs Cloudflare Vectorize#

The “FTS5 vs vectors” debate is usually hand-wavy. Both sides cite plausible reasons, neither runs the same queries through both engines on the same corpus, and the conclusion is whichever one the author shipped. With identical data and identical queries you can measure exactly where each wins.

The result: FTS5 and Vectorize have non-overlapping strengths. The right answer for most knowledge-base workloads is “ship both” behind an opt-in flag — not pick one. This page is the measurements, the cost math, and the dual-engine pattern.