@settlemint/dalp-cli 3.1.32-main.42224863695 → 3.1.32-main.42251724874

package/dist/{openapi-surface-fy40kyc6.json → openapi-surface-tzad3wxk.json}

@@ -7130,7 +7130,7 @@
         {
           "name": "instrumentAdmin",
           "in": "query",
-          "required": true,
+          "required": false,
           "description": "Canton party identifier, as the party registry or a platform read spells it.",
           "type": "string",
           "enum": null,
@@ -7266,7 +7266,7 @@
         {
           "name": "instrumentAdmin",
           "in": "query",
-          "required": true,
+          "required": false,
           "description": "Canton party identifier, as the party registry or a platform read spells it.",
           "type": "string",
           "enum": null,
@@ -7626,7 +7626,7 @@
         {
           "name": "instrumentAdmin",
           "in": "query",
-          "required": true,
+          "required": false,
           "description": "Canton party identifier, as the party registry or a platform read spells it.",
           "type": "string",
           "enum": null,
@@ -43562,7 +43562,7 @@
           "name": "fileData",
           "in": "query",
           "required": true,
-          "description": "The declaration as CSV text with the header ownerReference,jurisdiction,quantity: one row per beneficial owner, with the nominee's own reference for the owner, the owner's ISO 3166-1 alpha-2 country, and the units held for the owner in the security's own units. At most 5000 rows.",
+          "description": "The declaration as CSV text with the header ownerReference,jurisdiction,quantity: one row per beneficial owner, with the nominee's own reference for the owner, the owner's ISO 3166-1 alpha-2 country, and the units held for the owner in the security's own units. At most 5000 rows. Optional columns legalName, idType, idNumber and investorCategory carry each owner's identity: when the header has any of them it must have legalName, and every row needs a legalName (at most 200 characters). idType (passport, national_id, drivers_license, tax_id, company_registration or lei) and idNumber (at most 64 printable ASCII characters) go together; investorCategory is retail, professional, institutional or eligible_counterparty. The identity columns are stored encrypted and only reporting readers can read them back.",
           "type": "string",
           "enum": null,
           "pattern": null,
@@ -44883,6 +44883,17 @@
             "3f1c9a26-4c1e-4a53-9c6a-9c9d3e1b7a11"
           ],
           "fields": []
+        },
+        {
+          "name": "Prefer",
+          "in": "header",
+          "required": false,
+          "description": "RFC 7240 preference; separate directives with commas. Absent or `respond-async` answers 202 Accepted at once with the queued transaction's status URL. `wait` waits for settlement up to 99 seconds; `wait=N` waits up to N seconds, clamped to 5 through 99. Every wait also ends before the request deadline. A write that settles in time answers with its settled result; one that has not answers the same 202 as async. `Preference-Applied` echoes the directives honoured. Poll `Location` after 202 instead of resubmitting. `dalp-no-funding-pause` fails a transaction the chain refuses for gas at once, instead of pausing it until its wallet is funded.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
         }
       ],
       "requestBodyDescription": "Restricts one wallet. The platform freezes the wallet on every token in scope where the caller holds the custodian role, and reports each token's outcome.",
@@ -45121,6 +45132,17 @@
             "3f1c9a26-4c1e-4a53-9c6a-9c9d3e1b7a11"
           ],
           "fields": []
+        },
+        {
+          "name": "Prefer",
+          "in": "header",
+          "required": false,
+          "description": "RFC 7240 preference; separate directives with commas. Absent or `respond-async` answers 202 Accepted at once with the queued transaction's status URL. `wait` waits for settlement up to 99 seconds; `wait=N` waits up to N seconds, clamped to 5 through 99. Every wait also ends before the request deadline. A write that settles in time answers with its settled result; one that has not answers the same 202 as async. `Preference-Applied` echoes the directives honoured. Poll `Location` after 202 instead of resubmitting. `dalp-no-funding-pause` fails a transaction the chain refuses for gas at once, instead of pausing it until its wallet is funded.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
         }
       ],
       "requestBodyDescription": "Lifts a restriction. The platform unfreezes the wallet on every token this restriction froze and leaves freezes it did not apply alone.",
@@ -46271,6 +46293,21 @@
               ],
               "fields": []
             },
+            {
+              "name": "origin",
+              "in": "query",
+              "required": false,
+              "description": null,
+              "type": "string",
+              "enum": null,
+              "pattern": null,
+              "examples": [
+                "issuer-signed",
+                "aggregator-adapter",
+                "external"
+              ],
+              "fields": []
+            },
             {
               "name": "scope",
               "in": "query",
@@ -48269,8 +48306,8 @@
       "method": "POST",
       "url": "/api/v2/system/role-sets",
       "summary": "Set system roles",
-      "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
-      "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
+      "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
+      "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
       "tags": [
         "Roles and permissions"
       ],
@@ -68273,7 +68310,12 @@
             "collateralRatio",
             "yieldCoverage",
             "yieldDistribution",
-            "periodSummary"
+            "periodSummary",
+            "flows",
+            "collateralHistory",
+            "yieldRunway",
+            "bondTimeline",
+            "concentration"
           ],
           "pattern": null,
           "examples": [
@@ -68305,6 +68347,69 @@
           "examples": [],
           "fields": []
         },
+        {
+          "name": "from",
+          "in": "query",
+          "required": false,
+          "description": "Start of the asked period as an ISO 8601 instant. With `to`, required for the periodSummary metric. With `interval` and `to`, the window of a chart metric.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
+        },
+        {
+          "name": "to",
+          "in": "query",
+          "required": false,
+          "description": "End of the asked period as an ISO 8601 instant. Must be after `from`.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
+        },
+        {
+          "name": "preset",
+          "in": "query",
+          "required": false,
+          "description": null,
+          "type": "string",
+          "enum": [
+            "allTime",
+            "ytd",
+            "trailing12Months",
+            "trailing6Months",
+            "trailing3Months",
+            "trailing1Month",
+            "trailing7Days",
+            "trailing24Hours"
+          ],
+          "pattern": null,
+          "examples": [
+            "allTime",
+            "ytd",
+            "trailing12Months"
+          ],
+          "fields": []
+        },
+        {
+          "name": "interval",
+          "in": "query",
+          "required": false,
+          "description": null,
+          "type": "string",
+          "enum": [
+            "hour",
+            "day"
+          ],
+          "pattern": null,
+          "examples": [
+            "hour",
+            "day"
+          ],
+          "fields": []
+        },
         {
           "name": "maxPoints",
           "in": "query",
@@ -68327,21 +68432,25 @@
           "fields": []
         },
         {
-          "name": "from",
+          "name": "compare",
           "in": "query",
           "required": false,
-          "description": "Start of the asked period as an ISO 8601 instant. With `to`, required for the periodSummary metric.",
+          "description": "Send prior to also get the period straight before the window, one entry per point.",
           "type": "string",
-          "enum": null,
+          "enum": [
+            "prior"
+          ],
           "pattern": null,
-          "examples": [],
+          "examples": [
+            "prior"
+          ],
           "fields": []
         },
         {
-          "name": "to",
+          "name": "since",
           "in": "query",
           "required": false,
-          "description": "End of the asked period as an ISO 8601 instant. Must be after `from`.",
+          "description": "Send the date of the newest point you hold to get only the buckets from that point on. The bucket that holds it is sent again, because it may still be filling.",
           "type": "string",
           "enum": null,
           "pattern": null,
@@ -68362,7 +68471,10 @@
           },
           "query": {
             "metric": "supplyChanges",
-            "maxPoints": "60"
+            "preset": "allTime",
+            "interval": "hour",
+            "maxPoints": "60",
+            "compare": "prior"
           }
         }
       ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@settlemint/dalp-cli",
-  "version": "3.1.32-main.42224863695",
+  "version": "3.1.32-main.42251724874",
   "private": false,
   "description": "CLI for the Digital Asset Lifecycle Platform — manage tokens, identities, compliance, and more from the command line.",
   "homepage": "https://settlemint.com",
@@ -42,6 +42,7 @@
     "build": "taskguard sh -c 'rm -rf dist && bun build src/bin.ts --target bun --format esm --no-deprecated-namespace-object-setters --sourcemap=external --outdir dist --entry-naming dalp.js && printf '\\''export {};\n'\\'' > dist/dalp.d.ts && bun dist/dalp.js --help > /dev/null'",
     "publint": "publint run --strict --pack bun",
     "attw": "archive=$(bun pm pack --destination \"$PWD\" --quiet | tail -n 1) && attw \"$archive\" --profile esm-only; code=$?; rm -f \"$archive\"; exit $code",
+    "check:pack": "taskguard bun tools/check-pack.ts",
     "publish": "cp ../LICENSE . && bun run --cwd .. publish-if-absent \"$PWD\"",
     "prepack": "cp ../LICENSE .",
     "test": "taskguard bun test --parallel=4 --randomize --preload @testkit/effect-bun-test/preload --conditions dalp-source ./tests/unit",
@@ -49,14 +50,14 @@
   },
   "dependencies": {
     "@modelcontextprotocol/server": "2.0.0-alpha.4",
-    "@settlemint/dalp-sdk": "3.1.32-main.42224863695",
+    "@settlemint/dalp-sdk": "3.1.32-main.42251724874",
     "incur": "0.7.1",
     "zod": "4.6.7"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "0.18.5",
-    "@testkit/effect-bun-test": "3.1.32-main.42224863695",
-    "@tools/typescript-config": "3.1.32-main.42224863695",
+    "@testkit/effect-bun-test": "3.1.32-main.42251724874",
+    "@tools/typescript-config": "3.1.32-main.42251724874",
     "@types/bun": "1.4.4",
     "publint": "0.3.25"
   },

package/src/generated/openapi-surface.json

@@ -7130,7 +7130,7 @@
         {
           "name": "instrumentAdmin",
           "in": "query",
-          "required": true,
+          "required": false,
           "description": "Canton party identifier, as the party registry or a platform read spells it.",
           "type": "string",
           "enum": null,
@@ -7266,7 +7266,7 @@
         {
           "name": "instrumentAdmin",
           "in": "query",
-          "required": true,
+          "required": false,
           "description": "Canton party identifier, as the party registry or a platform read spells it.",
           "type": "string",
           "enum": null,
@@ -7626,7 +7626,7 @@
         {
           "name": "instrumentAdmin",
           "in": "query",
-          "required": true,
+          "required": false,
           "description": "Canton party identifier, as the party registry or a platform read spells it.",
           "type": "string",
           "enum": null,
@@ -43562,7 +43562,7 @@
           "name": "fileData",
           "in": "query",
           "required": true,
-          "description": "The declaration as CSV text with the header ownerReference,jurisdiction,quantity: one row per beneficial owner, with the nominee's own reference for the owner, the owner's ISO 3166-1 alpha-2 country, and the units held for the owner in the security's own units. At most 5000 rows.",
+          "description": "The declaration as CSV text with the header ownerReference,jurisdiction,quantity: one row per beneficial owner, with the nominee's own reference for the owner, the owner's ISO 3166-1 alpha-2 country, and the units held for the owner in the security's own units. At most 5000 rows. Optional columns legalName, idType, idNumber and investorCategory carry each owner's identity: when the header has any of them it must have legalName, and every row needs a legalName (at most 200 characters). idType (passport, national_id, drivers_license, tax_id, company_registration or lei) and idNumber (at most 64 printable ASCII characters) go together; investorCategory is retail, professional, institutional or eligible_counterparty. The identity columns are stored encrypted and only reporting readers can read them back.",
           "type": "string",
           "enum": null,
           "pattern": null,
@@ -44883,6 +44883,17 @@
             "3f1c9a26-4c1e-4a53-9c6a-9c9d3e1b7a11"
           ],
           "fields": []
+        },
+        {
+          "name": "Prefer",
+          "in": "header",
+          "required": false,
+          "description": "RFC 7240 preference; separate directives with commas. Absent or `respond-async` answers 202 Accepted at once with the queued transaction's status URL. `wait` waits for settlement up to 99 seconds; `wait=N` waits up to N seconds, clamped to 5 through 99. Every wait also ends before the request deadline. A write that settles in time answers with its settled result; one that has not answers the same 202 as async. `Preference-Applied` echoes the directives honoured. Poll `Location` after 202 instead of resubmitting. `dalp-no-funding-pause` fails a transaction the chain refuses for gas at once, instead of pausing it until its wallet is funded.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
         }
       ],
       "requestBodyDescription": "Restricts one wallet. The platform freezes the wallet on every token in scope where the caller holds the custodian role, and reports each token's outcome.",
@@ -45121,6 +45132,17 @@
             "3f1c9a26-4c1e-4a53-9c6a-9c9d3e1b7a11"
           ],
           "fields": []
+        },
+        {
+          "name": "Prefer",
+          "in": "header",
+          "required": false,
+          "description": "RFC 7240 preference; separate directives with commas. Absent or `respond-async` answers 202 Accepted at once with the queued transaction's status URL. `wait` waits for settlement up to 99 seconds; `wait=N` waits up to N seconds, clamped to 5 through 99. Every wait also ends before the request deadline. A write that settles in time answers with its settled result; one that has not answers the same 202 as async. `Preference-Applied` echoes the directives honoured. Poll `Location` after 202 instead of resubmitting. `dalp-no-funding-pause` fails a transaction the chain refuses for gas at once, instead of pausing it until its wallet is funded.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
         }
       ],
       "requestBodyDescription": "Lifts a restriction. The platform unfreezes the wallet on every token this restriction froze and leaves freezes it did not apply alone.",
@@ -46271,6 +46293,21 @@
               ],
               "fields": []
             },
+            {
+              "name": "origin",
+              "in": "query",
+              "required": false,
+              "description": null,
+              "type": "string",
+              "enum": null,
+              "pattern": null,
+              "examples": [
+                "issuer-signed",
+                "aggregator-adapter",
+                "external"
+              ],
+              "fields": []
+            },
             {
               "name": "scope",
               "in": "query",
@@ -48269,8 +48306,8 @@
       "method": "POST",
       "url": "/api/v2/system/role-sets",
       "summary": "Set system roles",
-      "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
-      "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
+      "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
+      "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
       "tags": [
         "Roles and permissions"
       ],
@@ -68273,7 +68310,12 @@
             "collateralRatio",
             "yieldCoverage",
             "yieldDistribution",
-            "periodSummary"
+            "periodSummary",
+            "flows",
+            "collateralHistory",
+            "yieldRunway",
+            "bondTimeline",
+            "concentration"
           ],
           "pattern": null,
           "examples": [
@@ -68305,6 +68347,69 @@
           "examples": [],
           "fields": []
         },
+        {
+          "name": "from",
+          "in": "query",
+          "required": false,
+          "description": "Start of the asked period as an ISO 8601 instant. With `to`, required for the periodSummary metric. With `interval` and `to`, the window of a chart metric.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
+        },
+        {
+          "name": "to",
+          "in": "query",
+          "required": false,
+          "description": "End of the asked period as an ISO 8601 instant. Must be after `from`.",
+          "type": "string",
+          "enum": null,
+          "pattern": null,
+          "examples": [],
+          "fields": []
+        },
+        {
+          "name": "preset",
+          "in": "query",
+          "required": false,
+          "description": null,
+          "type": "string",
+          "enum": [
+            "allTime",
+            "ytd",
+            "trailing12Months",
+            "trailing6Months",
+            "trailing3Months",
+            "trailing1Month",
+            "trailing7Days",
+            "trailing24Hours"
+          ],
+          "pattern": null,
+          "examples": [
+            "allTime",
+            "ytd",
+            "trailing12Months"
+          ],
+          "fields": []
+        },
+        {
+          "name": "interval",
+          "in": "query",
+          "required": false,
+          "description": null,
+          "type": "string",
+          "enum": [
+            "hour",
+            "day"
+          ],
+          "pattern": null,
+          "examples": [
+            "hour",
+            "day"
+          ],
+          "fields": []
+        },
         {
           "name": "maxPoints",
           "in": "query",
@@ -68327,21 +68432,25 @@
           "fields": []
         },
         {
-          "name": "from",
+          "name": "compare",
           "in": "query",
           "required": false,
-          "description": "Start of the asked period as an ISO 8601 instant. With `to`, required for the periodSummary metric.",
+          "description": "Send prior to also get the period straight before the window, one entry per point.",
           "type": "string",
-          "enum": null,
+          "enum": [
+            "prior"
+          ],
           "pattern": null,
-          "examples": [],
+          "examples": [
+            "prior"
+          ],
           "fields": []
         },
         {
-          "name": "to",
+          "name": "since",
           "in": "query",
           "required": false,
-          "description": "End of the asked period as an ISO 8601 instant. Must be after `from`.",
+          "description": "Send the date of the newest point you hold to get only the buckets from that point on. The bucket that holds it is sent again, because it may still be filling.",
           "type": "string",
           "enum": null,
           "pattern": null,
@@ -68362,7 +68471,10 @@
           },
           "query": {
             "metric": "supplyChanges",
-            "maxPoints": "60"
+            "preset": "allTime",
+            "interval": "hour",
+            "maxPoints": "60",
+            "compare": "prior"
           }
         }
       ]