Skip to main content
GET
Get detailed metrics including storage growth and object counts. The response splits stats into two database-wide collections: data.knowledge_collection (Knowledge) and data.memory_collection (User memories), each with its own row count. Counts aggregate across all collections in the database.

Behavior notes

row_count is chunks, not sources. One ingested document typically becomes many chunks (e.g., a 30-page PDF can produce 100+ rows). To count distinct sources, use List Documents with page_size=1 and read total.
  • Both collections always exist: Even if you’ve only ingested knowledge (or only memories), both collections are provisioned. Empty collections report row_count: 0.
  • Stats are eventually consistent: Immediately after ingestion or deletion, counts may lag until background processing completes. Check Ingestion Status for recently ingested IDs before treating counts as final.
Related Resources

Authorizations

Authorization
string
header
required

API key sent as a Bearer token: "Bearer prefix.secret"

Query Parameters

database
string
required

Database identifier

Example:

"acme_corp"

Response

OK

data
object
Example:
error
object

Error message, empty string on success.

Example:
meta
object
Example:
success
boolean

Whether the request succeeded.

Example:

true