List all extractors available to namespace

List all feature extractors available for use in this namespace.

This endpoint returns a unified view combining:

• Builtin extractors: Core extractors shipped with Mixpeek (text_extractor, image_extractor, etc.)
• Custom plugins: User-uploaded plugins at org or namespace level (Enterprise)

Each extractor includes:

• input_schema: JSON schema for input data validation
• output_schema: JSON schema for output document structure
• parameter_schema: JSON schema for configurable parameters
• required_vector_indexes: Vector indexes produced by this extractor
• feature_uri: URI to reference this extractor in collections

Use Cases:

• Discover available extractors when creating collections
• Get schema information for SDK code generation
• Check which custom plugins are deployed

Filtering:

• source=builtin: Only builtin extractors
• source=custom: Only custom plugins
• source=all (default): All extractors

GET /v1/namespaces/{namespace_id}/extractors

List all extractors available to namespace

cURL

curl --request GET \
  --url https://api.mixpeek.com/v1/namespaces/{namespace_id}/extractors

200

{
  "success": true,
  "extractors": [
    {
      "feature_extractor_name": "text_extractor",
      "version": "v1",
      "feature_extractor_id": "text_extractor_v1",
      "source": "builtin",
      "description": "Extract text embeddings from documents",
      "input_schema": {
        "type": "object"
      },
      "output_schema": {
        "type": "object"
      },
      "feature_uri": "mixpeek://text_extractor@v1/embedding"
    }
  ],
  "total": 8,
  "namespace_id": "ns_xxx",
  "builtin_count": 6,
  "custom_count": 2
}

Headers

Authorization · string

REQUIRED: Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.

Examples:

"Bearer YOUR_API_KEY"

"Bearer YOUR_STRIPE_API_KEY"

authorization · string

X-Namespace · string

Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like 'my-namespace'. Falls back to ?namespace= query parameter if the header is omitted.

Examples:

"ns_abc123def456"

"production"

"my-namespace"

Path Parameters

namespace_id · string · required

Query Parameters

source · enum<string> | null

Filter by extractor source (builtin, custom, or all)

Available options: builtin, custom, all

include_disabled · boolean · default: false

Include disabled/undeployed custom plugins

Response

200

application/json

List of all available extractors

Response for listing all extractors available to a namespace.

extractors · UnifiedExtractorResponse · object[] · required

List of all available extractors

Show child attributes

total · integer · required

Total number of extractors

namespace_id · string · required

Namespace ID

builtin_count · integer · required

Number of builtin extractors

custom_count · integer · required

Number of custom extractors (org + namespace level)

success · boolean · default: true

Whether the request succeeded