api-sdk-rb 1.11.111 → 1.11.133

data/spec/api/credits_api_spec.rb

@@ -32,19 +32,19 @@ describe 'CreditsApi' do
     end
   end
 
-  # unit tests for get_user_credit_balance_0
+  # unit tests for get_user_credit_balance
   # Get an account's credit balance
   # Returns the credits an account holds: the balance, and how much of it is reserved by operations that are still running.  An account reads its own balance; with a partner's API key, that is the account of the person who administers the partner. Widgetic administrators can read any account's. An account that has never held credits reads a balance of 0. `getPartnerCreditBalance` reads this same balance by partner id. 
   # @param user_id The account whose balance to read
   # @param [Hash] opts the optional parameters
   # @return [AccountCreditBalanceResponse]
-  describe 'get_user_credit_balance_0 test' do
+  describe 'get_user_credit_balance test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_user_credit_transactions_0
+  # unit tests for get_user_credit_transactions
   # List an account's credit ledger
   # Lists the entries of an account's credit ledger, newest first. This is also how an account's usage is read: every operation that spends credits is a `debit` entry, so summing the `debit` entries over a period gives the credits consumed in it, and the other types give what was added.  An account reads its own ledger; with a partner's API key, that is the account of the person who administers the partner. Widgetic administrators can read any account's. `getPartnerCreditTransactions` reads this same ledger by partner id.  The page is always bounded: `limit` defaults to 100 and is capped at 500, `offset` defaults to 0. 
   # @param user_id The account whose ledger to read
@@ -52,8 +52,8 @@ describe 'CreditsApi' do
   # @option opts [String] :transaction_type Only entries of this type, for instance `debit` for the credits spent. The types are listed on `AccountCreditTransaction`. 
   # @option opts [Integer] :limit Maximum number of entries to return
   # @option opts [Integer] :offset Number of entries to skip
-  # @return [GetPartnerCreditTransactions200Response]
-  describe 'get_user_credit_transactions_0 test' do
+  # @return [AccountCreditTransactionListResponse]
+  describe 'get_user_credit_transactions test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/entitlements_api_spec.rb

@@ -32,7 +32,7 @@ describe 'EntitlementsApi' do
     end
   end
 
-  # unit tests for get_managed_user_entitlements_0
+  # unit tests for get_managed_user_entitlements
   # Get managed user entitlements
   # Retrieves all entitlements for a managed user (admin or partner access).
   # @param managed_user_id Managed user ID
@@ -41,13 +41,13 @@ describe 'EntitlementsApi' do
   # @option opts [String] :feature Filter by specific feature
   # @option opts [String] :source Filter by entitlement source
   # @return [GetManagedUserEntitlementsResponse]
-  describe 'get_managed_user_entitlements_0 test' do
+  describe 'get_managed_user_entitlements test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_partner_entitlements_0
+  # unit tests for get_partner_entitlements
   # Get partner entitlements
   # Retrieves all entitlements for a partner (admin or partner access).
   # @param partner_id Partner ID
@@ -56,7 +56,7 @@ describe 'EntitlementsApi' do
   # @option opts [String] :feature Filter by specific feature
   # @option opts [String] :source Filter by entitlement source
   # @return [GetPartnerEntitlementsResponse]
-  describe 'get_partner_entitlements_0 test' do
+  describe 'get_partner_entitlements test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/invoices_api_spec.rb

@@ -32,7 +32,7 @@ describe 'InvoicesApi' do
     end
   end
 
-  # unit tests for get_invoices_by_partner_id_0
+  # unit tests for get_invoices_by_partner_id
   # List a partner's invoices
   # Lists the invoices issued to a partner, newest first. Each carries the price (`subtotal`), the tax on it (`taxAmount`) and what is paid (`total`), its status as the payment provider reports it, why the last payment failed (`failureReason`), and the page where it is paid (`hostedInvoiceUrl`).  A partner reads its own: the caller must be the person who administers the partner (an API key of that account works), and anyone else is refused with 403 whether or not the partner exists. Widgetic administrators can read any partner's and see exactly what the partner sees; the full records, with the internal fields, are `getAllInvoices` filtered by partner.  The page is always bounded: `limit` defaults to 50 and is capped at 100, `offset` defaults to 0. 
   # @param partner_id The partner whose invoices to list
@@ -41,7 +41,7 @@ describe 'InvoicesApi' do
   # @option opts [Integer] :limit Maximum number of invoices to return
   # @option opts [Integer] :offset Number of invoices to skip
   # @return [GetInvoicesByPartnerId200Response]
-  describe 'get_invoices_by_partner_id_0 test' do
+  describe 'get_invoices_by_partner_id test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/managed_users_api_spec.rb

@@ -32,7 +32,7 @@ describe 'ManagedUsersApi' do
     end
   end
 
-  # unit tests for copy_preset_for_managed_user_0
+  # unit tests for copy_preset_for_managed_user
   # Give a managed user a copy of one of your presets
   # Copies the preset `key` (see `setPartnerPreset`) onto a new canvas for one of your managed users, so their widget creator opens on a widget of their own that starts from yours. The copy is a draft widget in your account, filed under the managed user: `getAllWidgets` with `managedUserId` lists it, and no other managed user's editor can reach it.  The copy carries the preset's code, design and content schemas, and thumbnail, and starts from a fork of its code repository, so the user's chat edits begin where yours left off. It does not carry the preset's database or its compositions. It is not a preset itself, and changing or removing the preset afterwards never touches it.  To start a composition (the content and design editor) instead, you do not need a copy: call `createComposition` with the preset's `widgetId` (from `listPartnerPresets`) and the managed user.  The `Idempotency-Key` header is required (`400` without it). Send the same key when you retry, so one copy is made, not two. A copy that could not be made leaves nothing behind (503 `PRESET_COPY_FAILED`).  The managed user must be yours and active. 
   # @param id The managed user to give the copy to (Widgetic's id for the user)
@@ -41,13 +41,13 @@ describe 'ManagedUsersApi' do
   # @param [Hash] opts the optional parameters
   # @option opts [CopyPartnerPresetRequest] :copy_partner_preset_request 
   # @return [PartnerPresetCopyResponse]
-  describe 'copy_preset_for_managed_user_0 test' do
+  describe 'copy_preset_for_managed_user test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for create_composition_from_preset_0
+  # unit tests for create_composition_from_preset
   # Create a composition from one of your presets in one call
   # Validates the name, optional content, design, embed settings and locale, then creates a draft composition filed under the managed user, built on the preset's widget, in a single insert. A failure never leaves a half-made composition.  The preset's widget must be published. The managed user must be yours and active.  A widget that keeps what visitors send (a form, a vote, a rating) declares its tables in its own source (`src/lib/meta/database.json`); they are made for the composition here, in a schema of its own, as the widget was when it was last published. A widget that keeps nothing leaves the composition without tables. If the tables cannot be made just now, or the widget's file cannot be used, the composition is still created (`201`) and `meta.warnings` says why; the tables are made the next time the widget is generated.  The `Idempotency-Key` header is required (`400` without it). Send the same key when you retry, so one composition is created, not two. 
   # @param id 
@@ -55,52 +55,52 @@ describe 'ManagedUsersApi' do
   # @param idempotency_key Required: a call without it is refused with `400`. A key of your own that names this one request; a UUID is ideal. It is 8 to 50 characters of letters, digits, `-` and `_`. Send the same key again when you retry (after a timeout, a dropped connection or a `5xx`) and the call is carried out once: the retry gets the first answer back, marked `X-Idempotency-Cached: true`. The same key with a different body is refused with `422`, and a retry that arrives while the first call is still running with `409` (see `Retry-After`).
   # @param create_composition_from_preset_request 
   # @param [Hash] opts the optional parameters
-  # @return [CreateCompositionFromWidget201Response]
-  describe 'create_composition_from_preset_0 test' do
+  # @return [CompositionResponse]
+  describe 'create_composition_from_preset test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for create_managed_user_0
+  # unit tests for create_managed_user
   # Create Managed User
   # Creates a new managed user for a partner account.  The `Idempotency-Key` header is required (`400` without it). Send the same key when you retry, so one managed user is created, not two. 
   # @param idempotency_key Required: a call without it is refused with `400`. A key of your own that names this one request; a UUID is ideal. It is 8 to 50 characters of letters, digits, `-` and `_`. Send the same key again when you retry (after a timeout, a dropped connection or a `5xx`) and the call is carried out once: the retry gets the first answer back, marked `X-Idempotency-Cached: true`. The same key with a different body is refused with `422`, and a retry that arrives while the first call is still running with `409` (see `Retry-After`).
   # @param new_managed_user 
   # @param [Hash] opts the optional parameters
   # @return [ManagedUserResponse]
-  describe 'create_managed_user_0 test' do
+  describe 'create_managed_user test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for create_managed_user_editor_session_0
+  # unit tests for create_managed_user_editor_session
   # Create an editor session for a managed user
-  # Makes a short-lived credential that lets the browser of ONE of your managed users use Widgetic's editor pieces, such as the File Browser and the composition editor, without your API key ever reaching that browser. Call this from your server when the page that hosts the editor opens, and hand the `token` in the answer to that page.  The token is shown once. It starts with `wgt_ses_` and the browser sends it as `Authorization: Bearer <token>`. It can do only what the `surfaces` you name allow, and only for this managed user:  - `files`: upload a file (`uploadsPost`) and list the files uploaded for this user (`uploadsGet`). Every   file is filed for this user and stored in your own storage destination, never in Widgetic's: a file a   customer uploads is yours to keep, and takes none of your storage allowance. Partner storage is not   optional, so no session, whatever its surfaces, can be made until you have set a destination   (`setPartnerStorageDestination`); until then it is refused with 409 and `PARTNER_STORAGE_REQUIRED`, and   when the destination cannot be used with 503 and `STORAGE_DESTINATION_UNAVAILABLE`. A destination you   remove after the session was made stops its uploads too (the same 409; the browser is only told that   the feature is not available right now). To keep a customer from uploading, leave `files` out of the   session and hand the editors your own media library instead (`mediaLibrary`). - `editor`: edit one of this user's compositions: read it (`getCompositionById`, its content, design,   embed settings and schemas), check a content change (`validateCompositionContent`), and change its   name, content, design and embed settings (`updateComposition`, `setDynamicContent`). For a widget that   answers visitors' questions from documents (the `ai-answers` adapter), it also lists those documents,   adds one as text or as a file (a text file or a picture; a PDF once PDFs are read), and removes one   (`getAiAnswersKnowledge`, `addAiAnswersKnowledgeDocument`, `addAiAnswersKnowledgeFile`,   `removeAiAnswersKnowledgeDocument`); adding costs no credits, and is limited for each of your users   separately. It can reach   only compositions you created for this managed user (tag them with `managedUserId` when you create   them); any other composition, including another of your users', answers 404. - `creator`: use Widgetic's widget creator for this user, including its AI. Draw on canvases and save   them (`getAllCanvases`, `getCanvas`, `createCanvas`, `updateCanvas`, `previewDeleteCanvas`,   `deleteCanvas`); make, change, copy and delete the widgets on them (`createWidget`, `getWidgets`,   `getWidgetsBatch`, `updateWidget`, `uploadWidgetThumbnail`, `duplicateWidget`, `deleteWidget`);   list and make the compositions of a widget it built (`getAllCompositions`, `createComposition`), which   is how it shows the widget with sample values; keep the   conversation of each widget (`getConversationsByWidgetId`, `createConversationForWidget`,   `updateConversation`, `getMessages`, `createMessage`, `updateMessage`, `restoreCheckpoint`); and read a   widget's schemas and give it its repository (`getWidgetContentSchema`, `getWidgetDesignSchema`,   `updateWidgetRepository`). The AI that builds a widget is part of it: list the models   (`agentModelsGet`), open the widget's repository (`agentRepositoriesPost`,   `agentRepositoriesRepoIdGet`), start a generation and follow or cancel it (`agentCodeGeneratePost`,   `operationsStreamGet`, `operationsIdGet`, `operationsIdCancelPost`), build and preview the result   (`agentWidgetBuilderRepoHeadWidgetIdGet`, `buildWidgetFromRepo`, `previewWidgetVersion`), publish a   version of the widget and move between its versions (`agentWidgetBuilderPublishWidgetIdPost`,   `getWidgetPublishHistory`, `setWidgetPublishHistoryLive`, `renameWidgetPublishHistoryTitle`), and   turn a stroke or a sentence into a decision (`agentShapeRecognizePost`, `agentDesignResolvePost`). It can   also offer the customer your presets as starting points: read them and ask for a copy for this customer   (`listMyPresets`, `copyMyPreset`; you choose the presets with `setPartnerPreset`).   What the session makes is filed for this managed user, and the lists it reads hold only this user's   canvases, widgets and compositions. It can reach only canvases, widgets, compositions, repositories,   uploaded files and operations made for this managed user (tag the canvases and widgets you create   with `managedUserId`); any other canvas, widget, composition, conversation, message, repository, file   or operation, including another of your users', answers 404. The creator also saves the composition   it is editing (`updateComposition`, from the `editor` surface) and attaches pictures to its chat   (`uploadsPost`, from the `files` surface), and the surfaces do not imply one another: to open the   whole creator for a user, ask for `creator`, `editor` and `files` together. A generation or a build   one user starts can be followed and cancelled by that user and by you, never by another of your   users. The AI is paid for by your account, as your own calls are: its credits and allowances are   yours. A session cannot make a widget public (publishing a version does not), file one under a   project or an organization, or set anything the creator does not set: a body with another field is   refused with 403 and `EDITOR_SESSION_FIELD_NOT_ALLOWED`. - `workflows`: use Widgetic's Workflows editor for this user. List their workflows and the compositions   a workflow of theirs can chain (`listWorkspaceWorkflows`, `listWorkspaceWorkflowCompositionOptions`);   list the starting points you offer them and make a workflow from one, which gives the user their own copy   of every widget it chains, a composition of their own on each copy, and a draft   (`listWorkspaceWorkflowPresets`, `createWorkspaceWorkflowFromPreset`; you offer them with   `setPartnerWorkflowPreset`);   make, open, change and delete one (`createWorkspaceWorkflow`, `getWorkspaceWorkflow`,   `saveWorkspaceWorkflow`, `deleteWorkspaceWorkflow`) and copy it (`duplicateWorkspaceWorkflow`); publish   it or discard the changes of its draft (`publishWorkspaceWorkflow`,   `discardWorkspaceWorkflowChanges`); read and restore its versions (`listWorkspaceWorkflowVersions`,   `getWorkspaceWorkflowVersion`, `restoreWorkspaceWorkflowVersion`); pause, resume, archive and unarchive it   (`pauseWorkspaceWorkflow`, `resumeWorkspaceWorkflow`, `archiveWorkspaceWorkflow`,   `unarchiveWorkspaceWorkflow`); and read its counts (`getWorkspaceWorkflowStats`). The workspace in each   path is `personal`: a session has no other, and a path that names an organization is refused. What the   session makes is filed for this managed user (`managedUserId`), the lists hold only this user's workflows,   and it can reach only workflows made for this managed user; any other workflow, including one of yours   or of another of your users, answers 404. A workflow can chain only the compositions you made for this   managed user (tag them with `managedUserId`): one that belongs to anybody else is not available, and   publishing a workflow that uses it is refused. A customer can have at most 50 workflows, and what a   customer's session reads never says who published a version. A session cannot set who a workflow belongs   to or which workspace it is in: a body with another field is refused with 403 and   `EDITOR_SESSION_FIELD_NOT_ALLOWED`.  Everything else is refused with 403 and `EDITOR_SESSION_ROUTE_NOT_ALLOWED`: a session cannot read your account, make more sessions, change your presets or delete a composition, and a session without the `creator` surface cannot create or list compositions. Create the composition yourself with your API key, then open the editor on it.  A session ends at `expiresAt` (at most four hours), when you end it (`revokeManagedUserEditorSession`), or when the managed user is switched off or deleted. A managed user can have at most 100 live sessions at once (`429 EDITOR_SESSION_LIMIT_REACHED`). A session that is bound to a web page (`allowedOrigin`) is refused from any other origin.  The AI the session runs is paid for with your credits. Set `maxCredits` to hold the session to a number of them: once its generations have taken that many (a generation that fails is refunded and does not count), the next one is refused with 402 and `EDITOR_SESSION_CREDIT_LIMIT_REACHED`, and the browser is told only that the feature is not available right now. Without it, the limit Widgetic has set for your account applies when it has set one (the same limit for every session you make, and `maxCredits: null` asks for none), and otherwise the credits of your account are the only ceiling. What each of your users' sessions has spent is in `getManagedUserUsage`.  Each call makes a new session. It does not take an `Idempotency-Key`: the answer holds the token, and the token is never stored where a retry could read it back. The answer is sent with `Cache-Control: no-store`. 
+  # Makes a short-lived credential that lets the browser of ONE of your managed users use Widgetic's editor pieces, such as the File Browser and the composition editor, without your API key ever reaching that browser. Call this from your server when the page that hosts the editor opens, and hand the `token` in the answer to that page.  The token is shown once. It starts with `wgt_ses_` and the browser sends it as `Authorization: Bearer <token>`. It can do only what the `surfaces` you name allow, and only for this managed user:  - `files`: upload a file (`uploadFile`) and list the files uploaded for this user (`listUploads`). Every   file is filed for this user and stored in your own storage destination, never in Widgetic's: a file a   customer uploads is yours to keep, and takes none of your storage allowance. Partner storage is not   optional, so no session, whatever its surfaces, can be made until you have set a destination   (`setPartnerStorageDestination`); until then it is refused with 409 and `PARTNER_STORAGE_REQUIRED`, and   when the destination cannot be used with 503 and `STORAGE_DESTINATION_UNAVAILABLE`. A destination you   remove after the session was made stops its uploads too (the same 409; the browser is only told that   the feature is not available right now). To keep a customer from uploading, leave `files` out of the   session and hand the editors your own media library instead (`mediaLibrary`). - `editor`: edit one of this user's compositions: read it (`getCompositionById`, its content, design,   embed settings and schemas), check a content change (`validateCompositionContent`), and change its   name, content, design and embed settings (`updateComposition`, `setDynamicContent`). For a widget that   answers visitors' questions from documents (the `ai-answers` adapter), it also lists those documents,   adds one as text or as a file (a text file or a picture; a PDF once PDFs are read), and removes one   (`getAiAnswersKnowledge`, `addAiAnswersKnowledgeDocument`, `addAiAnswersKnowledgeFile`,   `removeAiAnswersKnowledgeDocument`); adding costs no credits, and is limited for each of your users   separately. It can reach   only compositions you created for this managed user (tag them with `managedUserId` when you create   them); any other composition, including another of your users', answers 404. - `creator`: use Widgetic's widget creator for this user, including its AI. Draw on canvases and save   them (`getAllCanvases`, `getCanvas`, `createCanvas`, `updateCanvas`, `previewDeleteCanvas`,   `deleteCanvas`); make, change, copy and delete the widgets on them (`createWidget`, `getWidgets`,   `getWidgetsBatch`, `updateWidget`, `uploadWidgetThumbnail`, `duplicateWidget`, `deleteWidget`);   list and make the compositions of a widget it built (`getAllCompositions`, `createComposition`), which   is how it shows the widget with sample values; keep the   conversation of each widget (`getConversationsByWidgetId`, `createConversationForWidget`,   `updateConversation`, `getMessages`, `createMessage`, `updateMessage`, `restoreCheckpoint`); and read a   widget's schemas and give it its repository (`getWidgetContentSchema`, `getWidgetDesignSchema`,   `updateWidgetRepository`). The AI that builds a widget is part of it: list the models   (`listLlmModels`), open the widget's repository (`createRepository`,   `getRepository`), start a generation and follow or cancel it (`generateCode`,   `streamOperationUpdates`, `getOperation`, `cancelOperation`), build and preview the result   (`getWidgetRepositoryHead`, `buildWidgetFromRepo`, `previewWidgetVersion`), publish a   version of the widget and move between its versions (`publishBuiltWidget`,   `getWidgetPublishHistory`, `setWidgetPublishHistoryLive`, `renameWidgetPublishHistoryTitle`), and   turn a stroke or a sentence into a decision (`recognizeShape`, `resolveDesignProperty`). It can   also offer the customer your presets as starting points: read them and ask for a copy for this customer   (`listMyPresets`, `copyMyPreset`; you choose the presets with `setPartnerPreset`).   What the session makes is filed for this managed user, and the lists it reads hold only this user's   canvases, widgets and compositions. It can reach only canvases, widgets, compositions, repositories,   uploaded files and operations made for this managed user (tag the canvases and widgets you create   with `managedUserId`); any other canvas, widget, composition, conversation, message, repository, file   or operation, including another of your users', answers 404. The creator also saves the composition   it is editing (`updateComposition`, from the `editor` surface) and attaches pictures to its chat   (`uploadFile`, from the `files` surface), and the surfaces do not imply one another: to open the   whole creator for a user, ask for `creator`, `editor` and `files` together. A generation or a build   one user starts can be followed and cancelled by that user and by you, never by another of your   users. The AI is paid for by your account, as your own calls are: its credits and allowances are   yours. A session cannot make a widget public (publishing a version does not), file one under a   project or an organization, or set anything the creator does not set: a body with another field is   refused with 403 and `EDITOR_SESSION_FIELD_NOT_ALLOWED`. - `workflows`: use Widgetic's Workflows editor for this user. List their workflows and the compositions   a workflow of theirs can chain (`listWorkspaceWorkflows`, `listWorkspaceWorkflowCompositionOptions`);   list the starting points you offer them and make a workflow from one, which gives the user their own copy   of every widget it chains, a composition of their own on each copy, and a draft   (`listWorkspaceWorkflowPresets`, `createWorkspaceWorkflowFromPreset`; you offer them with   `setPartnerWorkflowPreset`);   make, open, change and delete one (`createWorkspaceWorkflow`, `getWorkspaceWorkflow`,   `saveWorkspaceWorkflow`, `deleteWorkspaceWorkflow`) and copy it (`duplicateWorkspaceWorkflow`); publish   it or discard the changes of its draft (`publishWorkspaceWorkflow`,   `discardWorkspaceWorkflowChanges`); read and restore its versions (`listWorkspaceWorkflowVersions`,   `getWorkspaceWorkflowVersion`, `restoreWorkspaceWorkflowVersion`); pause, resume, archive and unarchive it   (`pauseWorkspaceWorkflow`, `resumeWorkspaceWorkflow`, `archiveWorkspaceWorkflow`,   `unarchiveWorkspaceWorkflow`); and read its counts (`getWorkspaceWorkflowStats`). The workspace in each   path is `personal`: a session has no other, and a path that names an organization is refused. What the   session makes is filed for this managed user (`managedUserId`), the lists hold only this user's workflows,   and it can reach only workflows made for this managed user; any other workflow, including one of yours   or of another of your users, answers 404. A workflow can chain only the compositions you made for this   managed user (tag them with `managedUserId`): one that belongs to anybody else is not available, and   publishing a workflow that uses it is refused. A customer can have at most 50 workflows, and what a   customer's session reads never says who published a version. A session cannot set who a workflow belongs   to or which workspace it is in: a body with another field is refused with 403 and   `EDITOR_SESSION_FIELD_NOT_ALLOWED`.  Everything else is refused with 403 and `EDITOR_SESSION_ROUTE_NOT_ALLOWED`: a session cannot read your account, make more sessions, change your presets or delete a composition, and a session without the `creator` surface cannot create or list compositions. Create the composition yourself with your API key, then open the editor on it.  A session ends at `expiresAt` (at most four hours), when you end it (`revokeManagedUserEditorSession`), or when the managed user is switched off or deleted. A managed user can have at most 100 live sessions at once (`429 EDITOR_SESSION_LIMIT_REACHED`). A session that is bound to a web page (`allowedOrigin`) is refused from any other origin.  The AI the session runs is paid for with your credits. Set `maxCredits` to hold the session to a number of them: once its generations have taken that many (a generation that fails is refunded and does not count), the next one is refused with 402 and `EDITOR_SESSION_CREDIT_LIMIT_REACHED`, and the browser is told only that the feature is not available right now. Without it, the limit Widgetic has set for your account applies when it has set one (the same limit for every session you make, and `maxCredits: null` asks for none), and otherwise the credits of your account are the only ceiling. What each of your users' sessions has spent is in `getManagedUserUsage`.  Each call makes a new session. It does not take an `Idempotency-Key`: the answer holds the token, and the token is never stored where a retry could read it back. The answer is sent with `Cache-Control: no-store`. 
   # @param id The managed user the session is for (Widgetic's id for the user)
   # @param new_editor_session 
   # @param [Hash] opts the optional parameters
   # @return [EditorSessionResponse]
-  describe 'create_managed_user_editor_session_0 test' do
+  describe 'create_managed_user_editor_session test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for delete_managed_user_0
+  # unit tests for delete_managed_user
   # Delete Managed User
   # Deletes a managed user by ID. Its editor sessions end with it. What was filed under it (compositions, widgets, uploads) stays in your account, untagged.
   # @param id ID of the managed user to delete
   # @param [Hash] opts the optional parameters
-  # @return [DeleteManagedUser200Response]
-  describe 'delete_managed_user_0 test' do
+  # @return [ManagedUserRemovalResponse]
+  describe 'delete_managed_user test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_all_managed_users_0
+  # unit tests for get_all_managed_users
   # Get Managed Users
   # Retrieve the managed users you manage, with pagination support. (Admins see every partner's managed users.)
   # @param [Hash] opts the optional parameters
@@ -108,58 +108,58 @@ describe 'ManagedUsersApi' do
   # @option opts [Integer] :size Number of items per page
   # @option opts [String] :sort Sort field and direction, `<field>:<asc|desc>`. The field is `createdAt`, `updatedAt` or `externalId` (the snake_case spellings `created_at`, `updated_at` and `external_id` work too); `asc` or `desc` alone sorts by `createdAt`. Any other field is a 400.
   # @return [GetAllManagedUsers200Response]
-  describe 'get_all_managed_users_0 test' do
+  describe 'get_all_managed_users test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_managed_user_by_id_0
+  # unit tests for get_managed_user_by_id
   # Get Managed User By ID
   # Retrieves a specific managed user by ID.
   # @param id ID of the managed user to retrieve
   # @param [Hash] opts the optional parameters
   # @return [ManagedUserResponse]
-  describe 'get_managed_user_by_id_0 test' do
+  describe 'get_managed_user_by_id test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_managed_user_design_defaults_0
+  # unit tests for get_managed_user_design_defaults
   # Read design defaults for one managed user
   # @param id 
   # @param [Hash] opts the optional parameters
-  # @return [GetPartnerDesignDefaults200Response]
-  describe 'get_managed_user_design_defaults_0 test' do
+  # @return [DesignDefaultsResponse]
+  describe 'get_managed_user_design_defaults test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_managed_user_limits_0
+  # unit tests for get_managed_user_limits
   # Read monthly credit cap and usage for one managed user
   # @param id 
   # @param [Hash] opts the optional parameters
-  # @return [GetManagedUserLimits200Response]
-  describe 'get_managed_user_limits_0 test' do
+  # @return [ManagedUserLimitsResponse]
+  describe 'get_managed_user_limits test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_managed_user_storage_usage_0
+  # unit tests for get_managed_user_storage_usage
   # Storage used by one managed user's uploads
   # @param id 
   # @param [Hash] opts the optional parameters
   # @return [GetManagedUserStorageUsage200Response]
-  describe 'get_managed_user_storage_usage_0 test' do
+  describe 'get_managed_user_storage_usage test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_managed_user_usage_0
+  # unit tests for get_managed_user_usage
   # What a managed user's editor sessions spent
   # Says how many credits the editor sessions of one of your managed users took from your account over a period, in total and for each operation. A generation costs one credit, taken from your account when it starts; one that fails is refunded and is counted as refunded, not as spent.  Only what was spent through editor sessions is here, and only since usage was first recorded: what you spend with your API key, and anything from before, is not. Use it to see which of your users spend the most, or to charge them for it. To hold one session to a number of credits, set `max_credits` when you make it (`createManagedUserEditorSession`).  The period runs from `startDate` (included) to `endDate` (not included): the 30 days before now when you give neither, and at most 366 days. A date without a time is midnight UTC at the start of that day, so for all of October give `startDate=2026-10-01` and `endDate=2026-11-01`. 
   # @param id The managed user whose usage you want (Widgetic's id for the user)
@@ -167,13 +167,13 @@ describe 'ManagedUsersApi' do
   # @option opts [String] :start_date Start of the period, included: an ISO 8601 date (`2026-10-01`) or date-time with its offset (`2026-10-01T08:00:00Z`). Default: 30 days before `endDate`. 
   # @option opts [String] :end_date End of the period, not included, in the same forms. Default: now. It must be after `startDate`, by at most 366 days. 
   # @return [ManagedUserUsageResponse]
-  describe 'get_managed_user_usage_0 test' do
+  describe 'get_managed_user_usage test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_managed_users_by_manager_id_0
+  # unit tests for get_managed_users_by_manager_id
   # Get Managed Users By Manager
   # Retrieve managed users for a specific manager with pagination support.
   # @param manager_id ID of the manager
@@ -182,64 +182,85 @@ describe 'ManagedUsersApi' do
   # @option opts [Integer] :size Number of items per page
   # @option opts [String] :sort Sort field and direction, `<field>:<asc|desc>`. The field is `createdAt`, `updatedAt` or `externalId` (the snake_case spellings `created_at`, `updated_at` and `external_id` work too); `asc` or `desc` alone sorts by `createdAt`. Any other field is a 400.
   # @return [GetManagedUsersByManagerIdResponse]
-  describe 'get_managed_users_by_manager_id_0 test' do
+  describe 'get_managed_users_by_manager_id test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for revoke_managed_user_editor_session_0
+  # unit tests for list_managed_user_entries
+  # List entries across a managed user's compositions
+  # Merges eligible tables (time and id columns) across the managed user's compositions in global time order, then compositionId, table, and id (byte order). Only tables with both a time and an id column take part. Rate limit 30 requests per minute.
+  # @param id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :composition_id 
+  # @option opts [String] :table 
+  # @option opts [Integer] :limit 
+  # @option opts [String] :order `desc` (the default) lists the newest entry first, `asc` the oldest. Entries are sorted by their time, then by their id (compared as text, byte by byte) in the same direction, so the order of two entries made at the same instant is always the same; an entry with no time counts as the oldest. A table with no time column is sorted by its id. The managed-user feed sorts by time, then by composition id, table and id. 
+  # @option opts [Time] :since Only entries made at this time or later: `since` is INCLUSIVE (an entry made at exactly `since` is returned). A date and time with an offset, such as `2026-10-01T00:00:00Z`; anything else answers 400 `INVALID_SINCE`. An entry with no time never matches, and a table with no time column answers 400 `ENTRY_TABLE_HAS_NO_TIME`. 
+  # @option opts [Time] :_until Only entries made before this time: `until` is EXCLUSIVE (an entry made at exactly `until` is NOT returned), so `since=A&until=B` followed by `since=B&until=C` counts every entry once. Same form and same refusals as `since` (400 `INVALID_UNTIL`). 
+  # @option opts [String] :cursor 
+  # @option opts [Hash<String, String>] :context Host context filters as &#x60;context[key]&#x3D;value&#x60; (max 5 keys, counting dotted &#x60;context.key&#x60; too). Use &#x60;column.&lt;name&gt;&#x3D;value&#x60; for columns whose names collide with reserved parameters.
+  # @option opts [Hash<String, String>] :filter Column filters as &#x60;filter[columnName]&#x3D;value&#x60; (same meaning as bare &#x60;columnName&#x3D;value&#x60; or &#x60;column.columnName&#x3D;value&#x60;; max 10 column filters counting all spellings). A plain &#x60;filter&#x3D;value&#x60; still filters a column named &#x60;filter&#x60;.
+  # @return [ManagedUserEntriesPageSuccess]
+  describe 'list_managed_user_entries test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for revoke_managed_user_editor_session
   # End one editor session of a managed user
   # Ends the session at once: its token stops working on the next request (on another server of ours, within a few seconds). Ending a session that has already ended is fine. 
   # @param id The managed user the session is for
   # @param session_id The &#x60;sessionId&#x60; of the session, from &#x60;createManagedUserEditorSession&#x60;
   # @param [Hash] opts the optional parameters
-  # @return [DeleteManagedUser200Response]
-  describe 'revoke_managed_user_editor_session_0 test' do
+  # @return [ManagedUserRemovalResponse]
+  describe 'revoke_managed_user_editor_session test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for revoke_managed_user_editor_sessions_0
+  # unit tests for revoke_managed_user_editor_sessions
   # End every editor session of a managed user
   # Ends all of the managed user&#39;s live editor sessions at once, for example when the user signs out of your platform. Their tokens stop working on the next request (on another server of ours, within a few seconds). It is fine to call it for a user who has none. 
   # @param id The managed user whose sessions end
   # @param [Hash] opts the optional parameters
   # @return [RevokeManagedUserEditorSessionsResponse]
-  describe 'revoke_managed_user_editor_sessions_0 test' do
+  describe 'revoke_managed_user_editor_sessions test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for set_managed_user_design_defaults_0
+  # unit tests for set_managed_user_design_defaults
   # Set or clear design defaults for one managed user
   # Send &#x60;{ \&quot;design\&quot;: { ... } }&#x60; to store a JSON object (at most 64 KB, nesting depth 32), or &#x60;{ \&quot;design\&quot;: null }&#x60; to remove the override. New compositions for this customer merge this layer over the partner default and under the request body. 
   # @param id 
   # @param set_partner_design_defaults_request 
   # @param [Hash] opts the optional parameters
-  # @return [GetPartnerDesignDefaults200Response]
-  describe 'set_managed_user_design_defaults_0 test' do
+  # @return [DesignDefaultsResponse]
+  describe 'set_managed_user_design_defaults test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for set_managed_user_limits_0
+  # unit tests for set_managed_user_limits
   # Set or clear the monthly credit cap for one managed user
   # Send monthlyCredits as a whole number from 0 up to 2147483647 to cap what this customer&#39;s editor sessions may spend in a UTC calendar month, or null to remove the cap. The cap counts the credits the customer&#39;s sessions spent that month (refunded credits do not count) and applies to all of the customer&#39;s sessions together, beside any &#x60;max_credits&#x60; a single session was given. A cap of 0 stops all paid work by this customer until you raise it. The cap starts counting from the first of the month (UTC); a cap set below what was already spent this month stops further work at once. 
   # @param id 
   # @param set_managed_user_limits_request 
   # @param [Hash] opts the optional parameters
-  # @return [GetManagedUserLimits200Response]
-  describe 'set_managed_user_limits_0 test' do
+  # @return [ManagedUserLimitsResponse]
+  describe 'set_managed_user_limits test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for update_managed_user_0
+  # unit tests for update_managed_user
   # Update Managed User
   # Updates an existing managed user. Only &#x60;externalId&#x60;, &#x60;metadata&#x60; and &#x60;isActive&#x60; can change, and &#x60;metadata&#x60; is replaced as a whole, so send all of it. &#x60;isActive: false&#x60; switches the managed user off: what it already has stays, and nothing new can be filed under it until you send &#x60;isActive: true&#x60;. Switching it off also ends all of its editor sessions, and they do not come back when you switch it on again.  The &#x60;Idempotency-Key&#x60; header is required (&#x60;400&#x60; without it). 
   # @param id ID of the managed user to update
@@ -247,7 +268,7 @@ describe 'ManagedUsersApi' do
   # @param update_managed_user 
   # @param [Hash] opts the optional parameters
   # @return [ManagedUserResponse]
-  describe 'update_managed_user_0 test' do
+  describe 'update_managed_user test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/operations_api_spec.rb

@@ -32,13 +32,13 @@ describe 'OperationsApi' do
     end
   end
 
-  # unit tests for operations_id_get_0
+  # unit tests for get_operation
   # Get operation status
   # Follows work that carries on after the response that started it. Duplicating a composition, for one, answers 202 with an `operationId`: ask for that operation until its `status` is `completed` (or `failed`, with the reason in `error`). A finished duplication names the new composition in `metadata.newCompositionId`.  An operation belongs to the user who started it. Asking for somebody else's operation answers 404, exactly as for one that does not exist. Administrators may read any operation. 
   # @param id Operation identifier returned when the job was created.
   # @param [Hash] opts the optional parameters
-  # @return [OperationsIdGetResponse]
-  describe 'operations_id_get_0 test' do
+  # @return [GetOperationResponse]
+  describe 'get_operation test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end