@acedatacloud/sdk 2026.718.1 → 2026.727.0

package/dist/index.d.mts

@@ -3,7 +3,7 @@
  *
  * When the API returns `402 Payment Required`, the transport calls the
  * configured `PaymentHandler` to produce the extra headers (typically
- * `X-Payment`) to attach to the retry. This keeps the SDK free of any
+ * `PAYMENT-SIGNATURE`) to attach to the retry. This keeps the SDK free of any
  * chain-specific signing logic, and lets callers plug in a real x402
  * implementation such as `@acedatacloud/x402-client`.
  */
@@ -11,7 +11,9 @@
 interface PaymentRequirement {
     scheme: string;
     network: string;
-    maxAmountRequired: string;
+    amount?: string;
+    /** @deprecated Legacy challenge field. */
+    maxAmountRequired?: string;
     maxTimeoutSeconds?: number;
     resource?: string;
     description?: string;
@@ -34,7 +36,7 @@ interface PaymentHandlerContext {
 }
 /** Result a payment handler must return. */
 interface PaymentHandlerResult {
-    /** Extra headers to attach to the retry (must include `X-Payment`). */
+    /** Extra headers to attach to the retry (normally `PAYMENT-SIGNATURE`). */
     headers: Record<string, string>;
 }
 /** A callable that signs/settles a payment and returns retry headers. */
@@ -175,7 +177,18 @@ declare class Chat {
     constructor(transport: Transport);
 }
 
-/** Task polling abstraction. */
+/**
+ * Task polling for long-running operations.
+ *
+ * A generation call always returns a handle, never sometimes a handle and
+ * sometimes a plain object — the caller decides whether to wait. When the server
+ * answers synchronously (some endpoints do for fast or cached results) the
+ * handle is born already complete, so `wait()` returns immediately rather than
+ * polling for something that has already arrived.
+ *
+ * Kept behaviourally identical to the Python and Go implementations; a
+ * divergence here is a cross-language bug that only shows up in production.
+ */
 
 interface TaskHandleOptions {
     pollInterval?: number;
@@ -186,7 +199,11 @@ declare class TaskHandle {
     private pollEndpoint;
     private transport;
     private _result;
-    constructor(taskId: string, pollEndpoint: string, transport: Transport);
+    constructor(taskId: string, pollEndpoint: string, transport: Transport, submitted?: Record<string, unknown>);
+    get done(): boolean;
+    /** Artifact URLs, once completed. */
+    urls(): string[];
+    progress(): number | null;
     get(): Promise<Record<string, unknown>>;
     isCompleted(): Promise<boolean>;
     wait(opts?: TaskHandleOptions): Promise<Record<string, unknown>>;

package/dist/index.d.ts

@@ -3,7 +3,7 @@
  *
  * When the API returns `402 Payment Required`, the transport calls the
  * configured `PaymentHandler` to produce the extra headers (typically
- * `X-Payment`) to attach to the retry. This keeps the SDK free of any
+ * `PAYMENT-SIGNATURE`) to attach to the retry. This keeps the SDK free of any
  * chain-specific signing logic, and lets callers plug in a real x402
  * implementation such as `@acedatacloud/x402-client`.
  */
@@ -11,7 +11,9 @@
 interface PaymentRequirement {
     scheme: string;
     network: string;
-    maxAmountRequired: string;
+    amount?: string;
+    /** @deprecated Legacy challenge field. */
+    maxAmountRequired?: string;
     maxTimeoutSeconds?: number;
     resource?: string;
     description?: string;
@@ -34,7 +36,7 @@ interface PaymentHandlerContext {
 }
 /** Result a payment handler must return. */
 interface PaymentHandlerResult {
-    /** Extra headers to attach to the retry (must include `X-Payment`). */
+    /** Extra headers to attach to the retry (normally `PAYMENT-SIGNATURE`). */
     headers: Record<string, string>;
 }
 /** A callable that signs/settles a payment and returns retry headers. */
@@ -175,7 +177,18 @@ declare class Chat {
     constructor(transport: Transport);
 }
 
-/** Task polling abstraction. */
+/**
+ * Task polling for long-running operations.
+ *
+ * A generation call always returns a handle, never sometimes a handle and
+ * sometimes a plain object — the caller decides whether to wait. When the server
+ * answers synchronously (some endpoints do for fast or cached results) the
+ * handle is born already complete, so `wait()` returns immediately rather than
+ * polling for something that has already arrived.
+ *
+ * Kept behaviourally identical to the Python and Go implementations; a
+ * divergence here is a cross-language bug that only shows up in production.
+ */
 
 interface TaskHandleOptions {
     pollInterval?: number;
@@ -186,7 +199,11 @@ declare class TaskHandle {
     private pollEndpoint;
     private transport;
     private _result;
-    constructor(taskId: string, pollEndpoint: string, transport: Transport);
+    constructor(taskId: string, pollEndpoint: string, transport: Transport, submitted?: Record<string, unknown>);
+    get done(): boolean;
+    /** Artifact URLs, once completed. */
+    urls(): string[];
+    progress(): number | null;
     get(): Promise<Record<string, unknown>>;
     isCompleted(): Promise<boolean>;
     wait(opts?: TaskHandleOptions): Promise<Record<string, unknown>>;