Update Organization
Update organization settings (requires ADMIN permission).
Security: Infrastructure configuration cannot be modified via this endpoint. Infrastructure updates require Mixpeek admin access via private endpoints.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Partial update payload for organization metadata.
Updated display name for the organization.
Updated organization logo URL (e.g., custom logo to override auto-generated logo).
Updated billing contact email.
Set the opt-in single address that receives alert/system notifications (None leaves it unchanged via exclude_unset).
Replace metadata with provided dictionary when set.
Per-org rate-limit overrides (merged on top of tier defaults).
Map of provider names to secret names for org-wide LLM credentials.
Toggle NSFW upload classification + hard-reject for this organization. Applies only to SHARED-plane tenants (infrastructure is None). None leaves the current setting unchanged.
Toggle fail-closed behaviour for the NSFW gate (reject uploads when the classifier is unavailable instead of allowing them). None leaves the current setting unchanged.
Response
Successful Response
Response model for organization endpoints.
SECURITY: Does NOT expose internal_id to prevent leakage of high-entropy secrets. Only organization_id (public identifier) is included in API responses.
Account tier with monthly credit allocations.
Tiers: FREE: 1,000 credits/month - Limited modalities, shared compute PRO: 100,000 credits/month - All modalities, dedicated namespace TEAM: 1,000,000 credits/month - Shared buckets, retrieval DAGs ENTERPRISE: Custom credits - Dedicated Ray cluster, SLA
free, pro, team, enterprise Rate limits by operation type (requests per minute).
The rate limiting system uses 5 categories aligned with actual resource consumption:
Categories: metadata: Infrastructure and configuration operations (namespaces, collections, retrievers, taxonomies, clusters CRUD). Zero-credit operations with highest rate limits.
data: Data operations (objects, documents CRUD). Low-credit operations with
high rate limits.
search: Search and retrieval operations (retriever/taxonomy execution).
Medium-credit operations with moderate rate limits.
upload: File upload operations (credit-intensive: 1 credit/MB). Variable-credit
operations with lower rate limits.
compute: Compute operations (cluster execution, batch processing). High-credit
operations (10 credits/min video) with lowest rate limits.Rate Limit Strategy: Higher limits for low-cost operations (metadata, data) Lower limits for high-cost operations (upload, compute) This aligns API throttling with actual infrastructure costs
Examples: - Creating a namespace: Uses 'metadata' category (fast, cheap) - Uploading a file: Uses 'upload' category (slow, expensive per MB) - Executing a retriever: Uses 'search' category (moderate cost) - Running batch processing: Uses 'compute' category (very expensive)

