@celigo/api-specs 0.2.50 → 0.2.51

package/dist/subscription.yml

@@ -1062,31 +1062,43 @@ components:
                     example: POC – HubSpot → Snowflake
     EndpointUsage:
       type: object
-      description: Endpoint entitlement usage.
+      description: |-
+        Endpoint entitlement usage for the requesting environment. An endpoint is a connected
+        application, not a connection record: connections that share a Celigo-managed application
+        profile (`assistant`) are one endpoint, generic HTTP connections without one are grouped by
+        `baseURI`, databases by `rdbms` engine and host, and other adaptor types by their own connection
+        identity (for example host and port). Each `endpoints[]` entry carries the fields it was grouped by.
       properties:
         numConsumed:
           type: integer
-          description: Number of endpoints currently consumed.
+          description: |-
+            Endpoints counted against the entitlement in the requesting environment, one per distinct
+            endpoint (see `endpoints`). Which flows bring an endpoint into the count follows the account's
+            pricing model, as for `flowUsage.numEnabled`: flows that are enabled on plans that meter
+            enabled resources, flows that ran in the billing period on plans that meter runs.
+          x-celigo-ai-guidance:
+            - Read the account license before interpreting this number. On run-metered plans an endpoint whose flows are enabled but have not run this period is not counted, and one used by a flow that ran even once counts for the whole period; on enabled-metered plans it is counted while any enabled flow references one of its connections, run or not.
+            - Connections referenced by no flow are never counted, and connections to the platform's own API (`api.integrator.io`) never count. On enabled-metered plans a connection referenced only by disabled flows is not counted; on run-metered plans an endpoint used by a flow that ran this period stays counted for the period even if that flow is disabled afterwards.
           example: 8
         endpoints:
           type: array
-          description: Detailed breakdown of endpoints by type.
+          description: The endpoints being counted, each with the connections that roll up into it.
+          x-celigo-ai-guidance:
+            - Two generic HTTP connections to the same application through different base URIs (a second store, a different API version in the path) are two endpoints; to explain an unexpected count, read each entry's `connections` and name the connection that carries the extra endpoint.
           items:
             type: object
             properties:
               type:
                 type: string
                 description: Endpoint adaptor type (e.g., `http`, `rdbms`, `ftp`).
-                x-celigo-ai-guidance:
-                  - Endpoint type/category.
                 example: http
               assistant:
                 type: string
-                description: Application assistant identifier, if the connection uses a Celigo-managed application profile (e.g., `hubspot`, `netsuite`).
+                description: Application assistant identifier, if the connection uses a Celigo-managed application profile (e.g., `hubspot`, `netsuite`). Connections sharing an assistant are one endpoint.
                 example: hubspot
               baseURI:
                 type: string
-                description: Base URI of the connection, if applicable.
+                description: Base URI that identifies this endpoint for generic HTTP connections (those without an `assistant`); connections whose base URIs differ are separate endpoints.
                 example: https://api.hubspot.com
               rdbms:
                 type: object

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.50",
+  "version": "0.2.51",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "aa43164",
+		"iasCommit": "f59fb30",
 		"generatedAt": "2026-09-24"
 	},
 	"roots": {