AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

cloudflare

Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.

Original source
cloudflare
License
Apache-2.0
Pinned revision
e44f580f9c4fa3bf268e284ae7706c7954ba31fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read cloudflare--cloudflare at revision e44f580f9c4fa3bf268e284ae7706c7954ba31fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 135

references/vectorize/api.md

Vectorize API routes

Fetch the relevant section of the Workers binding API before writing calls or types.

| Task | Current documentation | |------|-----------------------| | Vector shape, binding, and generated TypeScript types | Vectorize API | | Insert, upsert, retrieve by ID, delete, or inspect an index | Operations | | Query by vector or ID; choose returned metadata, values, and scoring precision | Query vectors and query options | | Filter by metadata, combine conditions, or use nested properties | Metadata filtering | | Batch ingestion and select vector formats | Insert vectors and current limits | | Manage indexes or vectors outside a Worker | Wrangler commands and REST API |

Operation choices

  • Choose insert when existing IDs should be preserved; choose upsert when they should be replaced. Upsert replaces the whole vector, including metadata, so provide the complete intended record.
  • Request only the values and metadata the caller needs. Indexed metadata can omit fields or truncate strings; full metadata and vector values change query limits and latency. Fetch the current query options before choosing a result count.
  • Treat accepted mutations and query visibility as separate events. Use current mutation guidance when implementing ingestion verification or read-after-write behavior.