Skip to main content
Dedicated infrastructure only. These endpoints are served by dedicated Enterprise deployments — they are not exposed on the shared public API at api.mixpeek.com, where they return 404/405. See Custom Extractors → Availability. Contact your account team to provision a dedicated deployment.Because this surface isn’t in the shared OpenAPI, it isn’t part of the auto-generated API Reference. This page is the hand-maintained contract; the reference client is server/scripts/api/plugins.py.
Naming. On this surface, custom extractors are addressed as plugins: the path segment is /plugins, and a deployed extractor’s plugin_id is {name}_{version} with dots replaced by underscores — e.g. text_embed@1.0.0text_embed_1_0_0. All endpoints are namespace-scoped and take Authorization: Bearer $MIXPEEK_API_KEY.
The CLI (python server/scripts/api/plugins.py push / deploy) wraps these calls. The raw HTTP flow:
Once DEPLOYED, reference the extractor’s feature_uri in a collection’s feature_extractor and in retriever feature_search stages exactly as you would a built-in — see the end-to-end walkthrough.

Endpoint reference

All paths are prefixed with /v1/namespaces/{namespace_id}.

Upload & deploy

Discover & inspect

Version management

Org plugins & namespace config

CLI equivalents

server/scripts/api/plugins.py is the maintained client for this surface (reads MIXPEEK_API_KEY, MIXPEEK_NAMESPACE, MIXPEEK_API_URL): See Custom Extractors for the full authoring guide and Local Development for lint/test.