You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit aeef6af
Browse filesBrowse the repository at this point in the historyBrowse files
| Standard | One public notebook; no new private notebooks (zero) | Permanent 1 GiB| The app needs neither a custom verification key nor a new private notebook. |
241
-
| Pro | One public notebook; five private notebooks | Permanent 6 GiB| The workflow needs a configurable `public_key` or any new private notebook. |
242
-
| Enterprise | One public notebook; ten private notebooks | Permanent 11 GiB| Admin-managed Enterprise workflows. Public SDK callers cannot create this type. |
240
+
| Standard | One public notebook; no new private notebooks (zero) | Permanent 100 MiB| The app needs neither a custom verification key nor a new private notebook. |
241
+
| Pro | One public notebook; five private notebooks | Permanent 100 MiB| The workflow needs a configurable `public_key` or any new private notebook. |
242
+
| Enterprise | One public notebook; ten private notebooks | Permanent 100 MiB| Admin-managed Enterprise workflows. Public SDK callers cannot create this type. |
243
243
244
244
Recommended behavior:
245
245
246
246
- Create Standard tokens by default.
247
247
- Create Pro tokens when the customer needs a configurable verification key or any new private notebook.
248
248
- Existing tokens can be upgraded from Standard to Pro, but cannot be downgraded.
249
-
- A Standard-to-Pro upgrade replaces that token's 1 GiB entitlement with 6 GiB; it does not produce 7 GiB.
249
+
- A Standard-to-Pro upgrade replaces the token type; storage entitlement stays 100 MiB and does not stack.
250
250
- Permanent capacity remains with the account after token retirement.
251
251
- A token type upgrade may consume quota or incur a billing charge.
252
252
- Store token IDs in the customer app database.
@@ -513,7 +513,7 @@ Additional constraints:
513
513
- Private notebook credentials must be unique under the same token.
514
514
- Private notebook credentials are optional at the SDK level, but apps that need credential-gated private metadata should explicitly pass `credential_val`.
515
515
- Notebook media is limited to detected image, audio, and video content. Each notebook accepts at most 500 current files, each file may be up to 100 MiB, and notebook text is limited to 10 MiB of UTF-8 data.
516
-
- Media consumes account capacity. Each acquired Standard, Pro, or Enterprise token contributes a permanent 1, 6, or 11 GiB entitlement respectively; available capacity may also include legacy credit and paid whole-GiB blocks.
516
+
- Media consumes account capacity. Each acquired Standard, Pro, or Enterprise token contributes a permanent 100 MiB entitlement; available capacity may also include legacy credit and paid whole-GiB blocks.
517
517
- Standard tokens cannot create new private notebooks. Existing Standard private notebooks are grandfathered and remain editable or deletable, but cannot be replaced after deletion.
518
518
- Pro tokens support five private notebooks, and Enterprise tokens support ten.
519
519
- If a token already has a public notebook, update the existing notebook instead of creating another one.
@@ -913,7 +913,7 @@ Recommended runtime flow:
913
913
- API keys are created in the OfSpectrum dashboard, not through the SDK.
914
914
- Token IDs, notebook IDs, media IDs, and current revisions should be stored in the customer app database.
915
915
- Standard tokens are the safest default for new workflows.
916
-
- Standard, Pro, and Enterprise tokens contribute permanent 1, 6, and 11 GiB account capacity respectively.
916
+
- Standard, Pro, and Enterprise tokens each contribute a permanent 100 MiB account capacity.
917
917
- Pro tokens are needed when the workflow requires a configurable `public_key` or up to five private notebooks; Enterprise creation is Admin-managed.
918
918
- Account defaults and storage charge authorization are configured in the Web Console, not through an API key.
919
919
- A staged save begins one session and reuses its `save_session_id` across all files and the commit.
0 commit comments