Skip to main content
GET
Database creation is asynchronous; check if your database is ready before executing ingestion or any queries. The response includes infra.ready_for_ingestion, a convenience flag derived from the four signals below. For a single check, read that field. The underlying signals are:
  • infra.ready_for_ingestion === true (derived: true only when all four signals below are true)
  • infra.scheduler_status === true (lifecycle provisioning has finished; false while the database is still being created, even if some collections already exist)
  • infra.graph_status === true (the graph layer)
  • infra.vectorstore_status.knowledge === true
  • infra.vectorstore_status.memories === true
Stale database IDs: If database does not exist, the call returns 404 DATABASE_NOT_FOUND. Always verify that the database was created successfully before polling. Querying too early: a POST /query sent before ready_for_ingestion is true returns 422 TENANT_INFRA_NOT_READY.
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 | null

Null on success; an object with code and message on failure.

Example:

null

meta
object
Example:
success
boolean

Whether the request succeeded.

Example:

true