Skip to main content

Browse the extractor catalog on GitHub

Runnable reference for every built-in Mixpeek extractor — inputs, parameters, output fields, embedding models, and copy-paste examples. Auto-generated from the live registry, so it always matches production.
Marketplace Deprecated. The self-service marketplace (publish/install/browse via /v1/plugins/... and /v1/public/plugins/...) has been removed. The SDK methods client.plugins.publish(), client.plugins.marketplace.list(), and client.plugins.install() no longer exist.Extractor sharing now uses the submission workflow described below.

How It Works

Instead of a self-service marketplace, community extractors follow a submission and review process:
  1. Develop — Build your extractor following the Custom Extractors guide
  2. Submit — Upload your extractor archive via POST /v1/extractors/submissions
  3. Review — The Mixpeek team reviews the submission for quality, security, and compatibility
  4. Merge — Approved extractors join the built-in catalog

Submitting an Extractor

Package your extractor as a zip archive and submit it for review:

Submission Requirements

  • Extractor must pass validation and security scan (same rules as custom extractor uploads)
  • Include a complete manifest.py with correct features definitions
  • Include working pipeline.py and optionally realtime.py
  • Archive must be under 500 MB

One-file YAML extractors

An archive that holds a single YAML manifest configures a built-in extractor instead of shipping code. It names the base with extends and can point the vector index at another embedding model, including one your organization uploaded (org:<model_id>). Set output.vector_index.dimensions to state the vector length the model returns. Validation runs one sample inference and rejects the extractor, with the traceback, when the vectors have another length or when the uploaded model’s recorded dimension differs. The index is always sized from the model.

Review Process

After submission:
  1. The archive is validated and scanned automatically
  2. The Mixpeek team reviews the extractor code for quality and security
  3. If approved, the extractor joins the built-in catalog
  4. The submitting organization is notified and the extractor becomes available to all users

Trust Tiers

Using Approved Extractors

Once an extractor is approved and merged, it works like any built-in extractor. Reference it by name and version in your collection configuration: