Skip to main content
GET
Returns row counts for a database: one for knowledge (data.knowledge_collection) and one for memories (data.memory_collection), each summed across every collection in the database. Use it to check how much a database holds.
row_count counts chunks, not sources: One ingested document typically becomes many chunks (for example, a 30-page PDF can produce 100+ rows). To count distinct sources, use List Context with page_size=1 and read pagination.total. Both stores always report: Both counts are returned even if you have ingested only knowledge or only memories. An empty store reports row_count: 0. Stats are eventually consistent: Immediately after ingestion or deletion, counts can lag until background processing completes. Check Ingestion Status for recently ingested IDs before treating counts as final.

Authorizations

Authorization
string
header
required

Send your API key as Authorization: Bearer <your_api_key>.

Query Parameters

database
string
required

Database identifier

Example:

"acme_corp"

Response

OK

data
TenantsTenantStatsResponse · object
Example:
error
HandlerApiError · object | null

Error details on failure, or null on success.

Example:

null

meta
HandlerResponseMeta · object
Example:
success
boolean

Whether the request succeeded.

Example:

true