Try it
button to try this API now in our playground. It’s the best way to check the full request and response in one place, customize your parameters, and generate ready-to-use code snippets.Sample Request
Query Parameters
- tenant_id: Required string - Primary organizational identifier (e.g., enterprise client, company) for multi-tenant data isolation
- sub_tenant_id: Optional string - Secondary organizational identifier (e.g., department, team, project) within a tenant for hierarchical data organization; defaults to tenant_id if not provided
Multi-Tenant Context
This API leverages Cortex’s hierarchical tenant system where:- Tenant Level: Stats for an entire organization (e.g., “acme_corp”)
- Sub-Tenant Level: Stats for specific departments or teams within an organization (e.g., “engineering” within “acme_corp”)
- Data Isolation: All statistics are completely isolated per tenant/sub-tenant combination
Response Details
- object_count: Number of objects/embeddings stored for the tenant
- vector_dimension: Dimension size of the embedding vectors for this tenant
- tenant_id: The name/identifier of the tenant
Use Cases
This API is useful for:- Monitoring: Track the number of embeddings stored for a tenant or department
- Validation: Verify vector dimensions before uploading new embeddings to ensure compatibility
- Analytics: Generate usage reports and statistics for billing, compliance, or optimization
- Capacity Planning: Understand storage requirements and usage patterns across organizations
- Multi-Tenant Management: Monitor data distribution across enterprise clients and their departments
- Department Insights: Compare usage patterns between different teams within the same organization
Example Scenarios
- Enterprise Dashboard:
tenant_id="acme_corp"
to see total company usage - Department Analytics:
tenant_id="acme_corp", sub_tenant_id="engineering"
for team-specific stats - Client Reporting: Generate individual reports for each enterprise client in your B2B platform
Error Responses
All endpoints return consistent error responses following the standard format. For detailed error information, see our Error Responses documentation.Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Query Parameters
Unique identifier for the tenant/organization
"tenant_1234"
Optional sub-tenant identifier used to organize data within a tenant. If omitted, the default sub-tenant created during tenant setup will be used.
"sub_tenant_4567"
Response
Successful Response
Total number of objects stored for this tenant
x >= 0
1
identifier for the tenant
1
"tenant_1234"
Dimensions of the vector embeddings used for this tenant. Null when the tenant is empty.
768
Indicates whether the stats retrieval was successful
true
Response message describing the operation result