Create a context
Created empty, and not queryable until you import sources and curate them — curate is explicit. Optionally seed a manifest. A work context is the exception: queryable from day zero, built from traces of work rather than documents.
POST /contexts
Parameters
Section titled “Parameters”X-Pinecone-Api-Version(header, string) — Date-based contract version, echoed back on the same header. Omit for the default (2026-07); sendunstablefor the in-development surface. An unrecognized value is rejected with400 unsupported_api_version.
Request body
Section titled “Request body”slug(body, string, required) — 3–64 chars, lowercase alnum + hyphens, starts with a lettername(body, string, required) — 1–128 charsdescription(body, string) — Free-text summary of what the context will hold.guide(body, string) — High-level standing instructions for the query runtime.manifest(body, object) — Seed manifest (validated against the manifest schema)kind(body, string) — How the context is built.search— built from source documents, and must be curated before it can be queried.work— built from traces of work done, queryable immediately, consolidated bygroomrather thancurate.pinecone_api_key(body, string) — Pinecone API key used to provision the context's managed index. Omit it under BYOC, where the deployment holds its own credential.
Responses
Section titled “Responses”200— The created context400— Invalid request403— Project not enabled for the Nexus preview (preview_not_enabled), or a per-plan context cap blocks creation.409— Slug already exists