Points Upsert And Payload

Agent upserts a point via PUT /collections/{name}/points with {id:42, vector:[...], payload:{title:'Widget', price:9.99}}.

Each point carries id (uint64 or UUID), vector(s) matching the collection's vector config, and an optional JSON payload. Upsert replaces the full point at that id (vector + payload) — to change only payload, use the payload endpoints instead so the vector is not required.

A point has payload {a:1, b:2}. Agent calls POST /collections/{name}/points/payload with payload={b:9, c:3} to update.

POST set-payload merges: the result is {a:1, b:9, c:3} — existing keys not in the request are preserved. To replace the entire payload (drop a), use the overwrite (PUT) payload operation instead. Know which verb merges vs overwrites.

Agent fetches points by id and sets with_vector=false, with_payload=['title'] to avoid pulling large vectors and unneeded payload.

Use with_vector=false and a with_payload key selector to return only needed fields, reducing response size and bandwidth. Request vectors only when the client genuinely needs them (e.g. re-ranking). Confirm the selected keys exist or handle absence.