Trigger an on-demand self-tuning optimize
Tunes the manifest from real query traffic and chains a forced re-curate. A body is required but every field in it is optional, so {} is valid — and a no-op when no candidate_queries are supplied. The context must have been curated, and only one optimize runs at a time.
Authorizations
Session token from POST /auth/login. Pass as Authorization: Bearer <token>. The alternative X-Pinecone-Api-Key header is also accepted for direct-key auth (used by the Nexus CLI on first contact).
Headers
Date-based contract version. Omit to resolve to the Nexus default version (2026-07, the oldest served version); send unstable for the in-development surface. The resolved version is echoed back on the same header. A present-but-unrecognized value is rejected with 400 unsupported_api_version.
Path Parameters
Context slug or UUID.
Body
Default 7200
Default 20
Default 200
Model-id overrides passed to the optimize runtime
Recent query records to tune toward (absent = no-op)
Task-token override; normally not needed
Response
Optimize enqueued (state: optimizing)
The uniform acknowledgment every context-workflow trigger returns. state is the forward-looking status; the per-workflow boolean flags are legacy and set only for the workflows that historically emitted them.