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.
How It Works
Instead of a self-service marketplace, community extractors follow a submission and review process:- Develop — Build your extractor following the Custom Extractors guide
- Submit — Upload your extractor archive via
POST /v1/extractors/submissions - Review — The Mixpeek team reviews the submission for quality, security, and compatibility
- 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.pywith correctfeaturesdefinitions - Include working
pipeline.pyand optionallyrealtime.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 withextends 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:- The archive is validated and scanned automatically
- The Mixpeek team reviews the extractor code for quality and security
- If approved, the extractor joins the built-in catalog
- The submitting organization is notified and the extractor becomes available to all users

