Get Organization
Get current organization details.
Security: Infrastructure configuration is NOT exposed via this endpoint. Infrastructure (Qdrant URLs, Ray clusters) is only accessible via private admin endpoints.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
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 (2026-07 pricing overhaul).
Current tiers (CC-required, tier minimum is a billing floor): BUILD: $25/mo min — 100K objects/mo (managed) / 1M vectors (MVS) SCALE: $250/mo min — 1M objects/mo (managed) / 25M vectors (MVS) ENTERPRISE: Custom — dedicated compute, SLA
LEGACY tiers — still stored on unmigrated orgs; resolvable until the Phase-4 migration completes (do NOT remove before then — org records in Mongo carry these strings): FREE (→ Build or read-only), PRO (→ Build), TEAM (→ Scale)
build, scale, enterprise, free, pro, team 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)

