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/configuration.md

Vectorize configuration routes

| Task | Current documentation | |------|-----------------------| | Create an index, choose dimensions and metric | Create indexes | | Bind an index to a Worker, develop, deploy, and verify queries | Introduction to Vectorize | | Configure bindings and generate types | Binding and TypeScript guidance | | Create, list, or delete metadata indexes | Metadata filtering and Wrangler commands | | Manage indexes and vectors through the CLI | Wrangler commands | | Upload NDJSON and batch ingestion | Insert vectors | | Check capacity, payload, namespace, or batch constraints | Limits |

Configuration decisions

Confirm the embedding model, output dimensions, and distance metric before provisioning: dimensions and metric cannot be changed in place. Plan a new index and re-embedding where needed when changing models.

Create metadata indexes before ingesting vectors that must be filterable. If adding one to an existing dataset, plan to re-upsert the affected vectors after index creation.

Choose metadata granularity around actual queries. For range filters over high-cardinality fields, consider buckets that preserve the application's required precision; do not bucket identifiers used for exact matches. Fetch the cardinality guidance before designing the schema.