@checkbox-site/node 0.1.1 → 0.2.1

package/dist/generated/operations.js

@@ -341,6 +341,23 @@ export const OPERATIONS = {
         paginated: false,
         summary: "Check domain verification now",
     },
+    resyncBilling: {
+        operationId: "resyncBilling",
+        namespace: "billings",
+        method: "resync",
+        httpMethod: "POST",
+        path: "/v1/sites/{site}/billing/resync",
+        pathParams: ["site"],
+        queryParams: [],
+        body: false,
+        idempotent: true,
+        auth: true,
+        scope: "sites:write",
+        response: "json",
+        list: false,
+        paginated: false,
+        summary: "Re-sync Stripe settings",
+    },
     createScan: {
         operationId: "createScan",
         namespace: "scans",
@@ -681,6 +698,23 @@ export const OPERATIONS = {
         paginated: false,
         summary: "List fix plans for a site",
     },
+    publishShopifyTerms: {
+        operationId: "publishShopifyTerms",
+        namespace: "fixes",
+        method: "publishShopifyTerms",
+        httpMethod: "POST",
+        path: "/v1/sites/{site}/fixes/shopify/publish",
+        pathParams: ["site"],
+        queryParams: [],
+        body: true,
+        idempotent: true,
+        auth: true,
+        scope: "fixes:write",
+        response: "json",
+        list: false,
+        paginated: false,
+        summary: "Publish the renewal terms to the Shopify app block",
+    },
     listEvidence: {
         operationId: "listEvidence",
         namespace: "evidence",
@@ -817,6 +851,23 @@ export const OPERATIONS = {
         paginated: false,
         summary: "Revoke a certificate",
     },
+    listNoticeSends: {
+        operationId: "listNoticeSends",
+        namespace: "noticeSends",
+        method: "list",
+        httpMethod: "GET",
+        path: "/v1/sites/{site}/notice_sends",
+        pathParams: ["site"],
+        queryParams: ["limit", "kind", "subscription", "include_samples"],
+        body: false,
+        idempotent: false,
+        auth: true,
+        scope: "notices:read",
+        response: "json",
+        list: true,
+        paginated: false,
+        summary: "List Checkbox Notices sends",
+    },
     retrieveNoticeSettings: {
         operationId: "retrieveNoticeSettings",
         namespace: "noticeSettings",
@@ -1565,6 +1616,23 @@ export const OPERATIONS = {
         paginated: false,
         summary: "Delete a registered checkout config",
     },
+    deleteSiteStripeCheckoutConfig: {
+        operationId: "deleteSiteStripeCheckoutConfig",
+        namespace: "siteStripeCheckoutConfigs",
+        method: "del",
+        httpMethod: "DELETE",
+        path: "/v1/sites/{site}/stripe_checkout_configs/{stripe_checkout_config}",
+        pathParams: ["site", "stripe_checkout_config"],
+        queryParams: [],
+        body: false,
+        idempotent: false,
+        auth: true,
+        scope: "test_runs:write",
+        response: "json",
+        list: false,
+        paginated: false,
+        summary: "Delete a registered checkout config (site path)",
+    },
     createTestRun: {
         operationId: "createTestRun",
         namespace: "testRuns",
@@ -1606,7 +1674,7 @@ export const OPERATIONS = {
         httpMethod: "GET",
         path: "/v1/test_runs/{test_run}",
         pathParams: ["test_run"],
-        queryParams: [],
+        queryParams: ["wait"],
         body: false,
         idempotent: false,
         auth: true,
@@ -1786,6 +1854,23 @@ export const OPERATIONS = {
         paginated: false,
         summary: "Send feedback",
     },
+    claimReviewPrompt: {
+        operationId: "claimReviewPrompt",
+        namespace: "reviewPrompts",
+        method: "claim",
+        httpMethod: "POST",
+        path: "/v1/sites/{site}/review_prompt",
+        pathParams: ["site"],
+        queryParams: [],
+        body: true,
+        idempotent: false,
+        auth: true,
+        scope: "compliance_plans:read",
+        response: "json",
+        list: false,
+        paginated: false,
+        summary: "Claim the one-time review prompt for a site",
+    },
 };
 /** `checkbox.device` */
 export class DeviceResource extends Resource {
@@ -1857,7 +1942,7 @@ export class SetupSessionsResource extends Resource {
     /**
      * Re-check the site now.
      *
-     * Loads the site (is the snippet live? which policy links does it have?), re-fetches the Terms and policies, re-evaluates compliance and queues the first synthetic-shopper scan. Call it after every change the agent made (and after deploying). Returns what was seen plus the updated session.
+     * Loads the site (is the snippet live? which policy links does it have?), re-fetches the Terms and policies, re-evaluates compliance and queues the first synthetic-shopper scan. While the domain is not verified: a live snippet (or the checkbox-verify meta tag) on the homepage verifies it now; otherwise a read-only scan of the site's own public pages is queued (unverified: no checkout is submitted). Call it after every change the agent made (and after deploying). Returns what was seen plus the updated session.
      *
      * @param setupSession Unique identifier of the setup session (setup_…).
      * @see POST /v1/setup_sessions/{setup_session}/verify (operation `verifySetupSession`, scope `setup_sessions:write`)
@@ -1892,7 +1977,7 @@ export class AccountResource extends Resource {
     /**
      * Update the account.
      *
-     * Pins the account to an API version (requests without a Checkbox-Version header use it). Known versions: 2026-10-30.
+     * Pins the account to an API version (requests without a Checkbox-Version header use it; known versions: 2026-10-30), sets the default retention, and turns the account-wide legal hold on or off. Retention and legal hold apply to the key's mode (test mode has its own).
      *
      * @see POST /v1/account (operation `updateAccount`, scope `account:write`)
      */
@@ -1925,7 +2010,7 @@ export class SitesResource extends Resource {
     /**
      * Retrieve a site.
      *
-     * Returns a site with its latest compliance verdict (score, status) and install details.
+     * Returns a site with its latest compliance status (label and counts) and install details.
      *
      * @param site Unique identifier of the site (site_…).
      * @see GET /v1/sites/{site} (operation `retrieveSite`, scope `sites:read`)
@@ -1973,7 +2058,7 @@ export class SitesResource extends Resource {
     /**
      * Connect a billing platform.
      *
-     * Connects the site's billing platform with read-only credentials (a Stripe restricted key, a Recharge token or a Shopify Admin API token), so Checkbox reads the customer-portal and reminder settings. Works for test-mode sites too (use an rk_test_ key). The credentials are validated by reading the settings once and stored encrypted.
+     * Connects the site's billing platform with the one restricted key (a Stripe restricted key, a Recharge token, a Shopify Admin API token, a Chargebee read-only API key, a Recurly private API key or a Paddle API key with read permissions), so Checkbox reads the customer-portal and reminder settings. Stripe: One Stripe restricted key per site: Read permissions for the checks, and Write permissions that Checkbox uses only after you click Approve on a fix, or in test mode (the one exception: Webhook Endpoints, used once to add Checkbox's webhook endpoint when you connect the key) (checklist: https://checkbox.site/docs/guides/stripe-key). A full secret key (sk_test_ / sk_live_) is refused on every path with test_key_not_restricted: use a restricted key. API keys and AI agents may connect TEST-mode keys (rk_test_…) only; a live key (rk_live_ / sk_live_) is refused with live_key_requires_dashboard, because only a person signed in to the Checkbox dashboard can connect one. The credentials are validated by reading the settings once and stored encrypted. When the key's Stripe account looks like another site's (the site's prices or Payment Links are not in it, or it is already connected in another workspace), nothing is connected and the error billing_account_mismatch asks the human to confirm; retry with confirm_account_mismatch: true only after they said yes. The account owner is emailed about every key connected.
      *
      * @param site Unique identifier of the site (site_…).
      * @see POST /v1/sites/{site}/integrations (operation `connectBillingPlatform`, scope `sites:write`)
@@ -2020,7 +2105,7 @@ export class DomainVerificationsResource extends Resource {
     /**
      * Check domain verification now.
      *
-     * Looks for the DNS TXT record and the /.well-known file now. On success in live mode, the account is activated and held monitoring starts.
+     * Looks for the DNS TXT record, the /.well-known file, and the site's Checkbox snippet or the checkbox-verify meta tag on https://<domain>/ now. On success in live mode, the account is activated and held monitoring starts.
      *
      * @param site Unique identifier of the site (site_…).
      * @see POST /v1/sites/{site}/domain_verification/check (operation `checkDomainVerification`, scope `sites:write`)
@@ -2029,6 +2114,20 @@ export class DomainVerificationsResource extends Resource {
         return this._request(OPERATIONS.checkDomainVerification, [site], undefined, options);
     }
 }
+/** `checkbox.billings` */
+export class BillingsResource extends Resource {
+    /**
+     * Re-sync Stripe settings.
+     *
+     * Re-reads the site's billing-platform settings now (Stripe customer-portal cancellation, trial-ending emails, plans) and re-evaluates the site, so a setting you just changed in Stripe shows up without waiting for the next scan. Every scan also re-reads them. Then poll retrieveLatestEvaluation (or listFindings) after about a minute.
+     *
+     * @param site Unique identifier of the site (site_…).
+     * @see POST /v1/sites/{site}/billing/resync (operation `resyncBilling`, scope `sites:write`)
+     */
+    resync(site, options) {
+        return this._request(OPERATIONS.resyncBilling, [site], undefined, options);
+    }
+}
 /** `checkbox.scans` */
 export class ScansResource extends Resource {
     /**
@@ -2080,7 +2179,7 @@ export class EvaluationsResource extends Resource {
     /**
      * List evaluations.
      *
-     * Verdicts newest first (score history), optionally for one site.
+     * Verdicts newest first (status history), optionally for one site.
      *
      * @see GET /v1/evaluations (operation `listEvaluations`, scope `evaluations:read`)
      */
@@ -2101,7 +2200,7 @@ export class EvaluationsResource extends Resource {
     /**
      * Get the current verdict of a site.
      *
-     * The latest evaluation of the site: is it compliant (score and status), and what blocks it. 404 resource_missing with next_action createScan when the site was never evaluated.
+     * The latest evaluation of the site: its compliance status and what blocks it. 404 resource_missing with next_action createScan when the site was never evaluated.
      *
      * @param site Unique identifier of the site (site_…).
      * @see GET /v1/sites/{site}/evaluation (operation `retrieveLatestEvaluation`, scope `evaluations:read`)
@@ -2115,7 +2214,7 @@ export class FindingsResource extends Resource {
     /**
      * List findings.
      *
-     * Findings ordered by urgency (failing first, then by severity). Filter by site, status (fail, needs_review, pass, not_applicable) and state (open, acknowledged, resolved, accepted_risk). Fix the open `fail` findings to become compliant.
+     * Findings ordered by urgency (failing first, then by severity). Filter by site, status (fail, needs_review, pass, not_applicable) and state (open, acknowledged, resolved, accepted_risk). Fix the open `fail` findings so the checks pass.
      *
      * @see GET /v1/findings (operation `listFindings`, scope `findings:read`)
      */
@@ -2150,7 +2249,7 @@ export class PlansResource extends Resource {
     /**
      * Get the compliance plan for a site.
      *
-     * Ordered tasks that make the site compliant, recomputed from its latest evaluation: each with the requirement and citation, where to change (file / URL / selector / Stripe object), the exact change (unified-diff template with machine-applicable edits, copy, or Stripe params) and how to verify it. Do plan.next_action: apply the first open task, call verifyTask, repeat until status is compliant. Tasks with status manual hold a question for the human (answerTask); they never block the others.
+     * Ordered tasks that make the site's checks pass, recomputed from its latest evaluation: each with the requirement and citation, where to change (file / URL / selector / Stripe object), the exact change (unified-diff template with machine-applicable edits, copy, or Stripe params) and how to verify it. Do plan.next_action: apply the first open task, call verifyTask, and repeat until the checks pass (status value compliant; status_label "Checks pass"). Tasks with status manual hold a question for the human (answerTask); they never block the others.
      *
      * @param site Unique identifier of the site (site_…).
      * @see GET /v1/sites/{site}/plan (operation `retrieveCompliancePlan`, scope `compliance_plans:read`)
@@ -2211,7 +2310,7 @@ export class VerificationsResource extends Resource {
     /**
      * Get a verification (long-poll with ?wait=30).
      *
-     * The verification's status (pending, passed, failed), expected vs observed per check, the diff and next_action. ?wait=N (≤ 30) holds the request until it resolves or N seconds pass.
+     * The verification's status (pending, passed, failed), expected vs observed per check, the diff and next_action. Also takes a task id (task_…): the newest verification of that task. ?wait=N (≤ 30) holds the request until it resolves or N seconds pass.
      *
      * @param verification Unique identifier of the verification (ver_…).
      * @see GET /v1/verifications/{verification} (operation `retrieveVerification`, scope `compliance_plans:read`)
@@ -2255,6 +2354,17 @@ export class FixesResource extends Resource {
     list(site, params, options) {
         return this._request(OPERATIONS.listSiteFixes, [site], params, options);
     }
+    /**
+     * Publish the renewal terms to the Shopify app block.
+     *
+     * For a Shopify store connected through the Checkbox Shopify app (site.shopify.connection = app): generates the renewal disclosure and consent label from the site's real plan, verifies them against the rules engine, and publishes them to the app-owned metafield the Checkbox "Renewal terms + consent" theme block reads. Nothing else in the store changes (no theme, product or checkout edits). The merchant places the block once in the theme editor (theme_editor_url); after that, publishing again updates the text the block shows. Then verify the sign-up task (verifyTask) or the site (verifySite). Errors: shopify_not_connected (only the merchant can install and connect the app; next_action has the step), terms_incomplete (problems lists the missing plan facts; next_action names the call that sets them), fix_verification_failed, platform_error (Shopify refused the write). In test mode it acts on test-mode sites, whose connected store is written the same way.
+     *
+     * @param site Unique identifier of the site (site_…).
+     * @see POST /v1/sites/{site}/fixes/shopify/publish (operation `publishShopifyTerms`, scope `fixes:write`, live mode needs an activated account)
+     */
+    publishShopifyTerms(site, params, options) {
+        return this._request(OPERATIONS.publishShopifyTerms, [site], params, options);
+    }
 }
 /** `checkbox.evidence` */
 export class EvidenceResource extends Resource {
@@ -2348,6 +2458,20 @@ export class CertificatesResource extends Resource {
         return this._request(OPERATIONS.revokeCertificate, [certificate], params, options);
     }
 }
+/** `checkbox.noticeSends` */
+export class NoticeSendsResource extends Resource {
+    /**
+     * List Checkbox Notices sends.
+     *
+     * Read-only: the emails Checkbox Notices sent, or tried to send, for this site (newest first), with status and, for a failed or skipped send, why. A test run's email steps name these rows (notices_send_log). Samples ("Send a test") are left out unless include_samples=true.
+     *
+     * @param site Unique identifier of the site (site_…).
+     * @see GET /v1/sites/{site}/notice_sends (operation `listNoticeSends`, scope `notices:read`)
+     */
+    list(site, params, options) {
+        return this._request(OPERATIONS.listNoticeSends, [site], params, options);
+    }
+}
 /** `checkbox.noticeSettings` */
 export class NoticeSettingsResource extends Resource {
     /**
@@ -2364,7 +2488,7 @@ export class NoticeSettingsResource extends Resource {
     /**
      * Update notice settings.
      *
-     * Chooses who sends the required emails (mode: merchant = you send them and Checkbox tracks them, the default; checkbox = Checkbox sends them), and sets branding, cancel_url and the confirmed cancellation policy. In checkbox mode, turning a notice on (enabled_kinds) requires cancel_url, a confirmed policy, a connected Stripe or Recharge account and a sending address; otherwise resource_conflict explains what is missing.
+     * Chooses who sends the required emails (mode: merchant = you send them and Checkbox tracks them, the default; checkbox = Checkbox sends them), and sets branding, cancel_url and the confirmed cancellation policy. add_kinds / remove_kinds turn single notices on or off and leave the others as they are; enabled_kinds replaces the whole list. In checkbox mode, turning a notice on requires cancel_url, a confirmed policy, a support email, a connected Stripe, Recharge, Chargebee, Recurly or Paddle account and a sending address; otherwise resource_conflict explains what is missing. The support email may be the Stripe account's public one (used automatically); the account owner's login address only after the human confirms it in the dashboard (support_email_to_confirm; an agent cannot confirm it). Turning notices on through the API never emails a real subscriber: on a test-mode site only test-run inboxes (and marked test copies to the owner) are emailed, and on a live site real subscribers are emailed only after a person confirms it once in the dashboard, after a preview (real_sends). The account owner is emailed when an agent turns notices on.
      *
      * @param site Unique identifier of the site (site_…).
      * @see POST /v1/sites/{site}/notice_settings (operation `updateNoticeSettings`, scope `notices:write`, live mode needs an activated account)
@@ -2468,7 +2592,7 @@ export class ChecksResource extends Resource {
     /**
      * Check checkout disclosure text.
      *
-     * Checks the automatic-renewal disclosure you are about to show next to a subscribe button: what it says (renewal until canceled, price, frequency, trial, term, how to cancel), where it sits (above the button, same page) and how it looks (size, contrast, set off), and the consent checkbox (present, not pre-checked). Returns the verdict per check and per legal requirement, plus `replacement`: compliant text and drop-in HTML generated from your price/interval/trial/cancel_url and verified by the engine. Call it whenever you write or change checkout copy. Stateless and deterministic: nothing is stored, the same input on the same as_of date gives the same verdicts. Every verdict comes from the Checkbox rules engine over the legal catalog (federal ROSCA / EFTA plus the state automatic-renewal laws); the response carries rules_version, catalog_version and a disclaimer (not legal advice). Read `verdict`, then `next_action`: it tells you exactly what to change and to call the check again until verdict is pass.
+     * Checks the automatic-renewal disclosure you are about to show next to a subscribe button: what it says (renewal until canceled, price, frequency, trial, term, how to cancel), where it sits (above the button, same page) and how it looks (size, contrast, set off), and the consent checkbox (present, not pre-checked). Returns the verdict per check and per legal requirement, plus `replacement`: suggested text that passes the checks and drop-in HTML (and the same markup as JSX for React) generated from your price/interval/trial/cancel_url and verified by the engine. Call it whenever you write or change checkout copy. Stateless and deterministic: nothing is stored, the same input on the same as_of date gives the same verdicts. Every verdict comes from the Checkbox rules engine over the legal catalog (federal ROSCA / EFTA plus the state automatic-renewal laws); the response carries rules_version, catalog_version and a disclaimer (not legal advice). Read `verdict`, then `next_action`: it tells you exactly what to change and to call the check again until verdict is pass.
      *
      * @see POST /v1/checks/disclosure (operation `checkDisclosure`, scope `checks:read`)
      */
@@ -2498,7 +2622,7 @@ export class ChecksResource extends Resource {
     /**
      * Check a subscription lifecycle email.
      *
-     * Checks the content of an acknowledgment (welcome) email, trial-ending reminder, renewal reminder, price-change notice, yearly terms reminder or cancellation confirmation against the requirements for that notice (renewal terms, amount, frequency, how to cancel, trial cancellation). The email is modelled as sent on time, so the verdict is about content; get send dates from checkNoticeSchedule. Returns `required_by` (requirements that make the email mandatory for this plan) and a compliant `template` with {{merge_tags}}, verified by the engine. Stateless and deterministic: nothing is stored, the same input on the same as_of date gives the same verdicts. Every verdict comes from the Checkbox rules engine over the legal catalog (federal ROSCA / EFTA plus the state automatic-renewal laws); the response carries rules_version, catalog_version and a disclaimer (not legal advice). Read `verdict`, then `next_action`: it tells you exactly what to change and to call the check again until verdict is pass.
+     * Checks the content of an acknowledgment (welcome) email, trial-ending reminder, renewal reminder, price-change notice, yearly terms reminder or cancellation confirmation against the requirements for that notice (renewal terms, amount, frequency, how to cancel, trial cancellation). The email is modelled as sent on time, so the verdict is about content; get send dates from checkNoticeSchedule. Prices are judged against what Stripe charges: with `site` (or, without it and without a price in terms, the account's one site with Stripe connected) the plan fields come from the site's plans and the email is matched to the plan it names ("Annual") first; a price that contradicts it fails, and `warnings` say which site and plan were used. Without `site`, a price you send in terms is judged as sent; when it differs from every plan of that site, the result is at most needs_review and Next is update_setup (update the site's plans first). Returns `required_by` (requirements that make the email mandatory for this plan) and a `template` that passes the checks, with {{merge_tags}}, verified by the engine. Stateless and deterministic: nothing is stored, the same input on the same as_of date gives the same verdicts. Every verdict comes from the Checkbox rules engine over the legal catalog (federal ROSCA / EFTA plus the state automatic-renewal laws); the response carries rules_version, catalog_version and a disclaimer (not legal advice). Read `verdict`, then `next_action`: it tells you exactly what to change and to call the check again until verdict is pass.
      *
      * @see POST /v1/checks/email (operation `checkEmail`, scope `checks:read`)
      */
@@ -2518,7 +2642,7 @@ export class ChecksResource extends Resource {
     /**
      * Get the dates each required notice must be sent.
      *
-     * For a subscription plan (price, interval, trial) and where you sell, returns every legally required notice — acknowledgment, trial-ending reminder, renewal reminders, yearly terms reminder, price-change notice — with the recommended send time and the compliant window (opens / closes), the jurisdictions each send satisfies and the citations. Uses the same timing as Checkbox Notices: per-state windows intersected, or the fewest sends that cover conflicting windows. Stateless. Check each email's content with checkEmail, or let Checkbox Notices send them.
+     * For a subscription plan (price, interval, trial) and where you sell, returns every legally required notice — acknowledgment, trial-ending reminder, renewal reminders, yearly terms reminder, price-change notice — with the recommended send time and the allowed send window (opens / closes), the jurisdictions each send satisfies and the citations. Uses the same timing as Checkbox Notices: per-state windows intersected, or the fewest sends that cover conflicting windows. Stateless. Check each email's content with checkEmail, or let Checkbox Notices send them.
      *
      * @see POST /v1/checks/notice_schedule (operation `checkNoticeSchedule`, scope `checks:read`)
      */
@@ -2691,7 +2815,7 @@ export class ReceiptsResource extends Resource {
     /**
      * Erase a subscriber's receipts.
      *
-     * For a subscriber's deletion request: deletes every receipt that matches customer_reference, email (hashed before the lookup) or checkout_session (optionally only for one site). The signed copy in the write-once evidence vault is kept but holds only a salted commitment to the subscriber's identifiers; erasing destroys the salt, so it can no longer be tied to the person. Pending attorney review.
+     * For a subscriber's deletion request: deletes every receipt that matches customer_reference, email (hashed before the lookup) or checkout_session (optionally only for one site). The signed copy in the write-once evidence vault is kept but holds only a salted commitment to the subscriber's identifiers; erasing destroys the salt, so it can no longer be tied to the person. Ask your counsel whether this meets a deletion request in your jurisdiction.
      *
      * @see POST /v1/receipts/erase (operation `eraseReceipts`, scope `receipts:write`)
      */
@@ -2758,7 +2882,7 @@ export class ReceiptSettingsResource extends Resource {
     /**
      * Update receipt settings.
      *
-     * Turn receipts on or off and set the retention in days (default 1461 = 4 years, the California UCL limitation period; pending attorney review). A new retention applies to receipts recorded afterwards.
+     * Turn receipts on or off and set the retention in days (default 1461 = 4 years: the California Unfair Competition Law limitation period; adjust to your counsel's advice). A new retention applies to receipts recorded afterwards.
      *
      * @see POST /v1/receipt_settings (operation `updateReceiptSettings`, scope `receipts:write`)
      */
@@ -2771,7 +2895,7 @@ export class TestCredentialsResource extends Resource {
     /**
      * Store a billing test-mode key.
      *
-     * Stores the site's Stripe TEST-mode key (rk_test_… preferred) used by test runs, after checking it with Stripe. Live keys are refused (test_key_not_test_mode). Least privilege: Write on Customers, Checkout Sessions, Subscriptions, Test clocks and Customer portal; Read on Prices, Products and Billing portal configuration. Replaces an existing key. Next: createTestRun.
+     * Stores the site's Stripe TEST-mode restricted key (rk_test_…), after checking it with Stripe the way the dashboard's Connect Stripe does. An agent may call this itself once the owner approved the setup; every store is logged on the site's setup timeline and Billing connection line, and the human can revoke it in one click. Live keys are refused (test_key_not_test_mode: a human adds live keys in the dashboard); a key whose Stripe account looks like another site's is refused with billing_account_mismatch until the human confirms (confirm_account_mismatch: true); secret keys (sk_test_…) are refused (test_key_not_restricted). On a test-mode site without a Stripe connection the key also becomes the site's Stripe connection: one key for checks, fixes (only after the human approves each) and test runs. The key's checklist: Customers: Write, Products: Read, Prices: Read, Coupons: Read, Subscriptions: Write, Test clocks: Write, Customer portal: Write, Checkout Sessions: Write, Payment Links: Write, Webhook Endpoints: Write. Replaces an existing key. Next: createTestRun.
      *
      * @param site Unique identifier of the site (site_…).
      * @see POST /v1/sites/{site}/test_credentials (operation `createTestCredential`, scope `test_runs:write`)
@@ -2812,7 +2936,7 @@ export class StripeCheckoutConfigsResource extends Resource {
     /**
      * Register the Checkout Session params your code uses.
      *
-     * Registers exactly the object your code passes to stripe.checkout.sessions.create (customer, URLs and secrets are not needed and are ignored). Test runs mirror it into Stripe test mode; when it matches your latest live checkout, the scanned test page counts as an observation of your live checkout. Re-register after changing your checkout code, then call createTestRun.
+     * Registers exactly the object your code passes to stripe.checkout.sessions.create (customer, URLs and secrets are not needed and are ignored; `warnings` says what was not stored). It is judged exactly like checkStripeCheckoutSession, discounts included. A config with the same name, or for the same Price ids, replaces the older one (`replaced`). Test runs mirror it into Stripe test mode; when it matches your latest live checkout, the scanned test page counts as an observation of your live checkout. Re-register after changing your checkout code, then call createTestRun.
      *
      * @param site Unique identifier of the site (site_…).
      * @see POST /v1/sites/{site}/stripe_checkout_configs (operation `createStripeCheckoutConfig`, scope `test_runs:write`)
@@ -2858,12 +2982,31 @@ export class StripeCheckoutConfigsResource extends Resource {
         return this.del(stripeCheckoutConfig, options);
     }
 }
+/** `checkbox.siteStripeCheckoutConfigs` */
+export class SiteStripeCheckoutConfigsResource extends Resource {
+    /**
+     * Delete a registered checkout config (site path).
+     *
+     * The same as deleteStripeCheckoutConfig, under the site path where configs are created and listed.
+     *
+     * @param site Unique identifier of the site (site_…).
+     * @param stripeCheckoutConfig Unique identifier of the stripe checkout config (scc_…).
+     * @see DELETE /v1/sites/{site}/stripe_checkout_configs/{stripe_checkout_config} (operation `deleteSiteStripeCheckoutConfig`, scope `test_runs:write`)
+     */
+    del(site, stripeCheckoutConfig, options) {
+        return this._request(OPERATIONS.deleteSiteStripeCheckoutConfig, [site, stripeCheckoutConfig], undefined, options);
+    }
+    /** Alias of `del()`. */
+    delete(site, stripeCheckoutConfig, options) {
+        return this.del(site, stripeCheckoutConfig, options);
+    }
+}
 /** `checkbox.testRuns` */
 export class TestRunsResource extends Resource {
     /**
      * Start a lifecycle test run.
      *
-     * Starts a synthetic test subscription in TEST mode and returns it queued. Stripe runs mirror your checkout into a test-mode Checkout Session, subscribe a test customer (card 4242) whose email is a Checkbox inbox, wait for your acknowledgment, advance a test clock through every legal notice window before trial end and renewal, cancel online in the customer portal and wait for the confirmation; then delete the test clock. Takes about 5-20 minutes: poll retrieveTestRun (next_action says when) or listen for test_run.completed. Each step reports observations, check results and agent-readable fixes; apply them and run again to verify.
+     * Starts a synthetic test subscription in TEST mode and returns it queued. Stripe runs mirror your checkout into a test-mode Checkout Session, subscribe a test customer (card 4242) whose email is a Checkbox inbox, wait for your acknowledgment, advance a test clock through every legal notice window before trial end and renewal, cancel online in the customer portal and wait for the confirmation; then delete the test clock. Usually takes 2-4 minutes (longer when your own emails are slow to arrive): poll retrieveTestRun (next_action says when) or listen for test_run.completed. Each step reports observations, check results and agent-readable fixes; apply them and run again to verify.
      *
      * @param site Unique identifier of the site (site_…).
      * @see POST /v1/sites/{site}/test_runs (operation `createTestRun`, scope `test_runs:write`, live mode needs an activated account)
@@ -2885,13 +3028,13 @@ export class TestRunsResource extends Resource {
     /**
      * Retrieve a test run.
      *
-     * The run with every step's status, observations, check results and fixes. While it runs, next_action.type is "wait"; when it finished, next_action says what to fix (apply_fixes / review_warnings) or "none".
+     * The run with every step's status, observations, check results and fixes. While it runs, next_action.type is "wait" and waiting_for says what it waits for; ?wait=30 answers as soon as the run moves on (or after 30 seconds). When it finished, next_action says what to fix (apply_fixes / review_warnings), retrieve_plan when the only warnings have nothing to change, or "none".
      *
      * @param testRun Unique identifier of the test run (run_…).
      * @see GET /v1/test_runs/{test_run} (operation `retrieveTestRun`, scope `test_runs:read`)
      */
-    retrieve(testRun, options) {
-        return this._request(OPERATIONS.retrieveTestRun, [testRun], undefined, options);
+    retrieve(testRun, params, options) {
+        return this._request(OPERATIONS.retrieveTestRun, [testRun], params, options);
     }
     /**
      * Cancel a test run.
@@ -3005,7 +3148,7 @@ export class FeedbacksResource extends Resource {
     /**
      * Send feedback.
      *
-     * Report a problem or a missing feature in Checkbox. Include what you tried, what happened and what you expected, and the site / request id when there is one. The Checkbox team reads every message. Rate limited to 20 per key per hour.
+     * Report a problem or a missing feature in Checkbox. Include what you tried, what happened and what you expected, and the site / request id when there is one. With type review, send a structured review of Checkbox the product (score 0-10, liked, disliked, wrong_verdicts, would_keep_using, stack) — only after the human said yes and saw the text. A review describes what worked or did not in Checkbox: it never states that the site broke a law or had unfixed problems, and carries no site names, URLs, customer data or quotes of the site's pages or emails (URLs are removed and no site is attached). Never include secrets or customer data: anything that looks like a secret, card number or email address is replaced with [redacted]. The Checkbox team reads every message. Rate limited to 20 per key per hour.
      *
      * @see POST /v1/feedback (operation `createFeedback`, scope `account:read`)
      */
@@ -3013,6 +3156,20 @@ export class FeedbacksResource extends Resource {
         return this._request(OPERATIONS.createFeedback, [], params, options);
     }
 }
+/** `checkbox.reviewPrompts` */
+export class ReviewPromptsResource extends Resource {
+    /**
+     * Claim the one-time review prompt for a site.
+     *
+     * The MCP tools call this when a site's compliance plan reaches status compliant, i.e. checks pass (including "Checks pass · N live checks pending"). show is true exactly once per site: the agent then asks the human once whether they want to send a quick review of Checkbox (createFeedback with type review), and sends it only on a yes, after showing the text. Never send a review without the human's yes.
+     *
+     * @param site Unique identifier of the site (site_…).
+     * @see POST /v1/sites/{site}/review_prompt (operation `claimReviewPrompt`, scope `compliance_plans:read`)
+     */
+    claim(site, params, options) {
+        return this._request(OPERATIONS.claimReviewPrompt, [site], params, options);
+    }
+}
 /** Resource namespaces of the client. */
 export const RESOURCES = {
     device: DeviceResource,
@@ -3020,6 +3177,7 @@ export const RESOURCES = {
     account: AccountResource,
     sites: SitesResource,
     domainVerifications: DomainVerificationsResource,
+    billings: BillingsResource,
     scans: ScansResource,
     evaluations: EvaluationsResource,
     findings: FindingsResource,
@@ -3029,6 +3187,7 @@ export const RESOURCES = {
     fixes: FixesResource,
     evidence: EvidenceResource,
     certificates: CertificatesResource,
+    noticeSends: NoticeSendsResource,
     noticeSettings: NoticeSettingsResource,
     notices: NoticesResource,
     lawUpdates: LawUpdatesResource,
@@ -3042,8 +3201,10 @@ export const RESOURCES = {
     receiptSettings: ReceiptSettingsResource,
     testCredentials: TestCredentialsResource,
     stripeCheckoutConfigs: StripeCheckoutConfigsResource,
+    siteStripeCheckoutConfigs: SiteStripeCheckoutConfigsResource,
     testRuns: TestRunsResource,
     webhookEndpoints: WebhookEndpointsResource,
     events: EventsResource,
     feedbacks: FeedbacksResource,
+    reviewPrompts: ReviewPromptsResource,
 };