API Reference
Limits
The size and count limits of one request, one memory, a search and a space name, in one table.
The limits a request runs into, in one place. Each page that a limit belongs to has the details and the error a request gets past it.
Requests and memories
| Limit | Value | Past it |
|---|---|---|
| One request body | 32 MiB (CORTEX_MAX_BODY_BYTES) | 413 PAYLOAD_TOO_LARGE |
| One memory's text (the indexed text of one experience) | 1 MiB | refused |
Memories per bulk save (POST /v1/experience/bulk) | 1,000 | 422 INVALID_BODY |
Lines per import request (POST /v1/import, JSON Lines) | 10,000 | 422 INVALID_BODY |
One export file (POST /v1/export) | 256 MiB | 413 EXPORT_TOO_LARGE, and nothing is returned: export in smaller scopes |
How long a retry key (idempotency_key) is remembered | 24 hours | a later save with the same key is a new save |
| Labels per memory | 4,096, each up to 262,144 UTF-8 bytes | 422 while CORTEX_LABEL_LIMITS=on (Experience Envelope) |
Search and answers
| Limit | Value | Past it |
|---|---|---|
Extra spaces in one search (extra_scopes) | 40 | 422 INVALID_EXTRA_SCOPES (Recall) |
Other wordings of a question (query_variants) | 4, each up to 4,096 bytes | 422 INVALID_BODY (Languages) |
Kinds whose newest memory every search includes (newest_of_kinds) | 16 | 422 INVALID_BODY |
Text handed to your model (budgets.max_tokens) | 4,000 tokens by default; you set it | a long memory comes as its best excerpt |
Spaces, tenants and shards
| Limit | Value |
|---|---|
| Parts (segments) in a space name | 32, and 4,096 characters in all (Scopes) |
| Copies of each shard in a cluster | 1 to 5 (3 is usual) |
| Per org tree, by default | 16 shared sources, 50,000 source containers per source, 8 applications; each is a setting, and past one a registration answers 409 ACCESS_LIMIT_REACHED (409 APP_LIMIT_REACHED for applications) |
Governed memory
| Limit | Value |
|---|---|
| Recent memories a policy test reads | up to 200 (Derivation Policies) |
| How long an unreviewed candidate waits | 30 days, then it expires (Review) |
| How far ahead a change set can be scheduled | 90 days (Change Sets) |
See also
- Error codes: every code a limit answers with.
- Plans and limits: what each CortexDB Cloud plan allows.