Skip to content
runlot
ReferenceAPIvectors

vectors

Covers 2 API operations in the vectors category.

MethodPathDescription
GET/v1/orgs/{orgSlug}/projects/{projectName}/vectorsVector store: namespaces, counts, widths and the plan's bounds (runlot vectors list)
DELETE/v1/orgs/{orgSlug}/projects/{projectName}/vectors/{namespace}Empties one namespace (runlot vectors delete)

GET /v1/orgs/{orgSlug}/projects/{projectName}/vectors

Requires viewer or higher. What env.vectors holds, namespace by namespace, read from the project's own database. A project that has never written a vector reads as empty, because the schema is installed on the first write. If the project's database cannot be reached, readError says so and the plan bounds are still returned.

limit and dimensionsMax are the plan's bounds (free 5,000 vectors and 3,072 dimensions, pro 25,000). exact is always true: search is exact k-NN, with no approximate index.

operationId getProjectVectors

Status codeDescriptionResponse body
200The namespaces and the boundsVectorOverview
403——
404——

DELETE /v1/orgs/{orgSlug}/projects/{projectName}/vectors/{namespace}

Requires member. Deletes every vector in the namespace and answers with the count. Irreversible, and the server asks for no confirmation — the CLI prompts for one unless you pass --yes. Audited as vectors.delete with the count. A namespace that does not exist answers 0.

operationId deleteVectorNamespace

Status codeDescriptionResponse body
200Deletedobject
400——
403——
404——
502console_unreachable — the project's database could not be reachedError

On this page