extend-ai 1.11.0 → 1.14.0

package/api/types/ExtractorVersion.d.ts

@@ -23,7 +23,7 @@ export interface ExtractorVersion {
     /**
      * The configuration settings for this version of the extractor. This is a union of two possible shapes:
      *
-     * - **[JSON Schema config](https://docs.extend.ai/2026-02-09/product/extraction/schema):** The current config format. All extractors created through this API version use this shape.
+     * - **[JSON Schema config](https://docs.extend.ai/2026-02-09/extraction/schema):** The current config format. All extractors created through this API version use this shape.
      * - **[Legacy config](https://docs.extend.ai/2025-04-21/product/legacy/legacy-schema):** A fields-array config from a previous API version. This shape is only returned for extractors that were originally configured with the legacy format. This API version does not support creating extractors with legacy configs.
      */
     config: Extend.ExtractConfig;

package/api/types/FileConversionStepDefinition.d.ts

@@ -2,7 +2,7 @@ import type * as Extend from "../index";
 /**
  * Converts files to a different format.
  *
- * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#file-conversion-step).
+ * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#file-conversion).
  */
 export interface FileConversionStepDefinition {
     name: string;

package/api/types/FileConversionStepDefinitionConfig.d.ts

@@ -3,7 +3,7 @@ export interface FileConversionStepDefinitionConfig {
     /**
      * Whether to continue or exit the workflow if file conversion fails. Defaults to `EXIT`.
      *
-     * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#file-conversion-step).
+     * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#file-conversion).
      */
     failureBehavior?: Extend.FileConversionStepDefinitionConfigFailureBehavior;
 }

package/api/types/FileConversionStepDefinitionConfigFailureBehavior.d.ts

@@ -1,7 +1,7 @@
 /**
  * Whether to continue or exit the workflow if file conversion fails. Defaults to `EXIT`.
  *
- * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#file-conversion-step).
+ * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#file-conversion).
  */
 export declare const FileConversionStepDefinitionConfigFailureBehavior: {
     readonly Continue: "CONTINUE";

package/api/types/FileConversionStepDefinitionConfigFailureBehavior.js

@@ -5,7 +5,7 @@ exports.FileConversionStepDefinitionConfigFailureBehavior = void 0;
 /**
  * Whether to continue or exit the workflow if file conversion fails. Defaults to `EXIT`.
  *
- * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#file-conversion-step).
+ * See the [File Conversion step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#file-conversion).
  */
 exports.FileConversionStepDefinitionConfigFailureBehavior = {
     Continue: "CONTINUE",

package/api/types/FileFromUrl.d.ts

@@ -3,7 +3,7 @@ export interface FileFromUrl {
     /**
      * A URL to download the file. For production use cases, we recommend using presigned URLs with a 5-15 minute expiration time.
      *
-     * Supported file types can be found [here](https://docs.extend.ai/2026-02-09/product/general/supported-file-types).
+     * Supported file types can be found [here](https://docs.extend.ai/2026-02-09/general/supported-file-types).
      */
     url: string;
     /** The name of the file. If not set, the file name is taken from the URL. */

package/api/types/HumanReviewStepDefinition.d.ts

@@ -2,7 +2,7 @@ import type * as Extend from "../index";
 /**
  * Pauses the workflow for human review in the dashboard.
  *
- * See the [Human Review step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#human-review-step).
+ * See the [Human Review step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#human-review).
  */
 export interface HumanReviewStepDefinition {
     name: string;

package/api/types/LegacyClassificationAdvancedOptions.d.ts

@@ -4,7 +4,7 @@ export interface LegacyClassificationAdvancedOptions {
     context?: Extend.LegacyClassificationAdvancedOptionsContext;
     /** Enable advanced multimodal processing for better handling of visual elements during classification. */
     advancedMultimodalEnabled?: boolean;
-    /** Limit processing to a specific number of pages from the beginning of the document. See [Page Ranges](https://docs.extend.ai/2026-02-09/product/page-ranges). */
+    /** Limit processing to a specific number of pages from the beginning of the document. See [Page Ranges](https://docs.extend.ai/2026-02-09/page-ranges). */
     fixedPageLimit?: number;
     pageRanges?: Extend.PageRanges;
 }

package/api/types/LegacyClassificationConfig.d.ts

@@ -1,8 +1,8 @@
 import type * as Extend from "../index";
 export interface LegacyClassificationConfig {
-    /** The base processor to use. For classifiers, this must be either `"classification_performance"` or `"classification_light"`. See [Classification Changelog](https://docs.extend.ai/2026-02-09/changelog/classification/classification-performance) for more details. */
+    /** The base processor to use. For classifiers, this must be either `"classification_performance"` or `"classification_light"`. See [Classification Changelog](https://docs.extend.ai/2026-02-09/model-versioning/classification/classification-performance) for more details. */
     baseProcessor?: Extend.LegacyClassificationConfigBaseProcessor;
-    /** The version of the `"classification_performance"` or `"classification_light"` processor to use. If this is provided, the `baseProcessor` must also be provided. See [Classification Changelog](https://docs.extend.ai/2026-02-09/changelog/classification/classification-performance) for more details. */
+    /** The version of the `"classification_performance"` or `"classification_light"` processor to use. If this is provided, the `baseProcessor` must also be provided. See [Classification Changelog](https://docs.extend.ai/2026-02-09/model-versioning/classification/classification-performance) for more details. */
     baseVersion?: string;
     /** Array of possible classifications for the document. */
     classifications: Extend.LegacyClassification[];

package/api/types/LegacyClassificationConfigBaseProcessor.d.ts

@@ -1,4 +1,4 @@
-/** The base processor to use. For classifiers, this must be either `"classification_performance"` or `"classification_light"`. See [Classification Changelog](https://docs.extend.ai/2026-02-09/changelog/classification/classification-performance) for more details. */
+/** The base processor to use. For classifiers, this must be either `"classification_performance"` or `"classification_light"`. See [Classification Changelog](https://docs.extend.ai/2026-02-09/model-versioning/classification/classification-performance) for more details. */
 export declare const LegacyClassificationConfigBaseProcessor: {
     readonly ClassificationPerformance: "classification_performance";
     readonly ClassificationLight: "classification_light";

package/api/types/LegacyClassificationConfigBaseProcessor.js

@@ -2,7 +2,7 @@
 // This file was auto-generated by Fern from our API Definition.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.LegacyClassificationConfigBaseProcessor = void 0;
-/** The base processor to use. For classifiers, this must be either `"classification_performance"` or `"classification_light"`. See [Classification Changelog](https://docs.extend.ai/2026-02-09/changelog/classification/classification-performance) for more details. */
+/** The base processor to use. For classifiers, this must be either `"classification_performance"` or `"classification_light"`. See [Classification Changelog](https://docs.extend.ai/2026-02-09/model-versioning/classification/classification-performance) for more details. */
 exports.LegacyClassificationConfigBaseProcessor = {
     ClassificationPerformance: "classification_performance",
     ClassificationLight: "classification_light",

package/api/types/LegacyDocumentProcessorRunCredits.d.ts

@@ -1,9 +1,9 @@
 /**
- * These are usage credits for document processing (extraction, classification, or splitting). File parsing credits are tracked separately and can be retrieved from the [Get File](https://docs.extend.ai/2026-02-09/developers/api-reference/endpoints/file/get-file) endpoint.
+ * These are usage credits for document processing (extraction, classification, or splitting). File parsing credits are tracked separately and can be retrieved from the [Get File](https://docs.extend.ai/2026-02-09/api-reference/endpoints/file/get-file) endpoint.
  *
  * This field will not be returned for processor runs created before October 7, 2025, or for customers on legacy billing systems.
  *
- * For more details on how credits work, see our [Credits Guide](https://docs.extend.ai/2026-02-09/product/general/how-credits-work).
+ * For more details on how credits work, see our [Credits Guide](https://docs.extend.ai/2026-02-09/general/how-credits-work).
  */
 export interface LegacyDocumentProcessorRunCredits {
     /** The number of credits consumed specifically for document processing in this processor run. This does not include file parsing credits. */

package/api/types/LegacyExtractionAdvancedOptions.d.ts

@@ -20,7 +20,7 @@ export interface LegacyExtractionAdvancedOptions {
      * and may include additional `insights` of type `issue` or `review_summary` to help identify
      * fields that may need manual review.
      *
-     * To learn more, view the [Review Agent Documentation](https://docs.extend.ai/2026-02-09/product/extraction/review-agent)
+     * To learn more, view the [Review Agent Documentation](https://docs.extend.ai/2026-02-09/extraction/review-agent)
      */
     reviewAgent?: Extend.LegacyExtractionAdvancedOptionsReviewAgent;
     /** Strategy for handling large arrays in documents. */
@@ -30,7 +30,7 @@ export interface LegacyExtractionAdvancedOptions {
     excelSheetRanges?: Extend.ExcelSheetRange[];
     /** Strategy for selecting sheets from Excel documents. */
     excelSheetSelectionStrategy?: Extend.LegacyExtractionAdvancedOptionsExcelSheetSelectionStrategy;
-    /** DEPRECATED - See [Page Ranges](https://docs.extend.ai/2026-02-09/product/page-ranges). */
+    /** DEPRECATED - See [Page Ranges](https://docs.extend.ai/2026-02-09/page-ranges). */
     fixedPageLimit?: number;
     pageRanges?: Extend.PageRanges;
 }

package/api/types/LegacyExtractionAdvancedOptionsReviewAgent.d.ts

@@ -4,7 +4,7 @@
  * and may include additional `insights` of type `issue` or `review_summary` to help identify
  * fields that may need manual review.
  *
- * To learn more, view the [Review Agent Documentation](https://docs.extend.ai/2026-02-09/product/extraction/review-agent)
+ * To learn more, view the [Review Agent Documentation](https://docs.extend.ai/2026-02-09/extraction/review-agent)
  */
 export interface LegacyExtractionAdvancedOptionsReviewAgent {
     /** Whether to enable the review agent for the extraction output. */

package/api/types/LegacyExtractionConfig.d.ts

@@ -1,15 +1,15 @@
 import type * as Extend from "../index";
 export interface LegacyExtractionConfig {
-    /** The base processor to use. For extractors, this must be either `"extraction_performance"` or `"extraction_light"`. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/changelog/extraction/extraction-performance) for more details. */
+    /** The base processor to use. For extractors, this must be either `"extraction_performance"` or `"extraction_light"`. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/model-versioning/extraction/extraction-performance) for more details. */
     baseProcessor?: Extend.LegacyExtractionConfigBaseProcessor;
-    /** The version of the `"extraction_performance"` or `"extraction_light"` processor to use. If this is provided, the `baseProcessor` must also be provided. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/changelog/extraction/extraction-performance) for more details. */
+    /** The version of the `"extraction_performance"` or `"extraction_light"` processor to use. If this is provided, the `baseProcessor` must also be provided. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/model-versioning/extraction/extraction-performance) for more details. */
     baseVersion?: string;
     /** Custom rules to guide the extraction process in natural language. */
     extractionRules?: string;
     /**
      * JSON Schema definition of the data to extract. Either `fields` or `schema` must be provided.
      *
-     * See the [JSON Schema guide](https://docs.extend.ai/2026-02-09/product/extraction/schema) for details and examples of schema configuration.
+     * See the [JSON Schema guide](https://docs.extend.ai/2026-02-09/extraction/schema) for details and examples of schema configuration.
      */
     schema?: Extend.JsonObject;
     /**

package/api/types/LegacyExtractionConfigBaseProcessor.d.ts

@@ -1,4 +1,4 @@
-/** The base processor to use. For extractors, this must be either `"extraction_performance"` or `"extraction_light"`. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/changelog/extraction/extraction-performance) for more details. */
+/** The base processor to use. For extractors, this must be either `"extraction_performance"` or `"extraction_light"`. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/model-versioning/extraction/extraction-performance) for more details. */
 export declare const LegacyExtractionConfigBaseProcessor: {
     readonly ExtractionPerformance: "extraction_performance";
     readonly ExtractionLight: "extraction_light";

package/api/types/LegacyExtractionConfigBaseProcessor.js

@@ -2,7 +2,7 @@
 // This file was auto-generated by Fern from our API Definition.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.LegacyExtractionConfigBaseProcessor = void 0;
-/** The base processor to use. For extractors, this must be either `"extraction_performance"` or `"extraction_light"`. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/changelog/extraction/extraction-performance) for more details. */
+/** The base processor to use. For extractors, this must be either `"extraction_performance"` or `"extraction_light"`. See [Extraction Changelog](https://docs.extend.ai/2026-02-09/model-versioning/extraction/extraction-performance) for more details. */
 exports.LegacyExtractionConfigBaseProcessor = {
     ExtractionPerformance: "extraction_performance",
     ExtractionLight: "extraction_light",

package/api/types/LegacyJsonOutputMetadataValue.d.ts

@@ -14,7 +14,7 @@ export interface LegacyJsonOutputMetadataValue {
      *
      * These scores will be present when the `reviewAgent.enabled` flag is set to `true` in the processor config.
      * If the review agent is enabled but a score is not returned for a field, this value will be `null`.
-     * To learn more, view the [Review Agent Documentation](https://docs.extend.ai/2026-02-09/product/extraction/review-agent)
+     * To learn more, view the [Review Agent Documentation](https://docs.extend.ai/2026-02-09/extraction/review-agent)
      */
     reviewAgentScore?: number | null;
     citations?: Extend.LegacyJsonOutputMetadataValueCitationsItem[];

package/api/types/LegacySplitterAdvancedOptions.d.ts

@@ -10,7 +10,7 @@ export interface LegacySplitterAdvancedOptions {
     splitMethod?: Extend.LegacySplitterAdvancedOptionsSplitMethod;
     /** For Excel documents, split by worksheet. */
     splitExcelDocumentsBySheetEnabled?: boolean;
-    /** Limit processing to a specific number of pages from the beginning of the document. See [Page Ranges](https://docs.extend.ai/2026-02-09/product/page-ranges). */
+    /** Limit processing to a specific number of pages from the beginning of the document. See [Page Ranges](https://docs.extend.ai/2026-02-09/page-ranges). */
     fixedPageLimit?: number;
     pageRanges?: Extend.PageRanges;
 }

package/api/types/LegacySplitterConfig.d.ts

@@ -1,8 +1,8 @@
 import type * as Extend from "../index";
 export interface LegacySplitterConfig {
-    /** The base processor to use. For splitters, this can currently only be `"splitting_performance"` or `"splitting_light"`. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/changelog/splitting/splitting-performance) for more details. */
+    /** The base processor to use. For splitters, this can currently only be `"splitting_performance"` or `"splitting_light"`. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/model-versioning/splitting/splitting-performance) for more details. */
     baseProcessor?: Extend.LegacySplitterConfigBaseProcessor;
-    /** The version of the `"splitting_performance"` or `"splitting_light"` processor to use. If this is provided, the `baseProcessor` must also be provided. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/changelog/splitting/splitting-performance) for more details. */
+    /** The version of the `"splitting_performance"` or `"splitting_light"` processor to use. If this is provided, the `baseProcessor` must also be provided. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/model-versioning/splitting/splitting-performance) for more details. */
     baseVersion?: string;
     /** Array of classifications that define the possible types of document sections. */
     splitClassifications: Extend.LegacyClassification[];

package/api/types/LegacySplitterConfigBaseProcessor.d.ts

@@ -1,4 +1,4 @@
-/** The base processor to use. For splitters, this can currently only be `"splitting_performance"` or `"splitting_light"`. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/changelog/splitting/splitting-performance) for more details. */
+/** The base processor to use. For splitters, this can currently only be `"splitting_performance"` or `"splitting_light"`. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/model-versioning/splitting/splitting-performance) for more details. */
 export declare const LegacySplitterConfigBaseProcessor: {
     readonly SplittingPerformance: "splitting_performance";
     readonly SplittingLight: "splitting_light";

package/api/types/LegacySplitterConfigBaseProcessor.js

@@ -2,7 +2,7 @@
 // This file was auto-generated by Fern from our API Definition.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.LegacySplitterConfigBaseProcessor = void 0;
-/** The base processor to use. For splitters, this can currently only be `"splitting_performance"` or `"splitting_light"`. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/changelog/splitting/splitting-performance) for more details. */
+/** The base processor to use. For splitters, this can currently only be `"splitting_performance"` or `"splitting_light"`. See [Splitting Changelog](https://docs.extend.ai/2026-02-09/model-versioning/splitting/splitting-performance) for more details. */
 exports.LegacySplitterConfigBaseProcessor = {
     SplittingPerformance: "splitting_performance",
     SplittingLight: "splitting_light",

package/api/types/MergeExtractStepDefinition.d.ts

@@ -2,7 +2,7 @@ import type * as Extend from "../index";
 /**
  * Merges extraction outputs from multiple upstream extract steps.
  *
- * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#merge-extract-step).
+ * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#merge-extract).
  */
 export interface MergeExtractStepDefinition {
     name: string;

package/api/types/MergeExtractStepDefinitionConfig.d.ts

@@ -3,7 +3,7 @@ export interface MergeExtractStepDefinitionConfig {
     /**
      * How to order fields when merging. Defaults to confidence.
      *
-     * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#merge-extract-step).
+     * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#merge-extract).
      */
     mergeOrder?: Extend.MergeExtractStepDefinitionConfigMergeOrder;
 }

package/api/types/MergeExtractStepDefinitionConfigMergeOrder.d.ts

@@ -1,7 +1,7 @@
 /**
  * How to order fields when merging. Defaults to confidence.
  *
- * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#merge-extract-step).
+ * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#merge-extract).
  */
 export declare const MergeExtractStepDefinitionConfigMergeOrder: {
     readonly Confidence: "confidence";

package/api/types/MergeExtractStepDefinitionConfigMergeOrder.js

@@ -5,7 +5,7 @@ exports.MergeExtractStepDefinitionConfigMergeOrder = void 0;
 /**
  * How to order fields when merging. Defaults to confidence.
  *
- * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#merge-extract-step).
+ * See the [Merge Extract step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#merge-extract).
  */
 exports.MergeExtractStepDefinitionConfigMergeOrder = {
     Confidence: "confidence",

package/api/types/PageRanges.d.ts

@@ -1,5 +1,5 @@
 import type * as Extend from "../index";
 /**
- * Limit processing to the specified page ranges. See [Page Ranges](https://docs.extend.ai/2026-02-09/product/page-ranges).
+ * Limit processing to the specified page ranges. See [Page Ranges](https://docs.extend.ai/2026-02-09/page-ranges).
  */
 export type PageRanges = Extend.PageRangesItem[];

package/api/types/ParseConfig.d.ts

@@ -16,7 +16,7 @@ export interface ParseConfig {
      * * Prefer `markdown` for most documents, multi-column reading order, and retrieval use cases
      * * Prefer `spatial` for messy/scanned/handwritten or skewed documents, when you need near 1:1 layout fidelity, or for BOL-like logistics docs
      *
-     * See “Markdown vs Spatial” in the [Parse guide](https://docs.extend.ai/2026-02-09/product/parsing/configuration-options#target-format) for details.
+     * See “Markdown vs Spatial” in the [Parse guide](https://docs.extend.ai/2026-02-09/parsing/configuration#target-format) for details.
      */
     target?: Extend.ParseConfigTarget;
     /** Strategy for dividing the document into chunks. */
@@ -24,7 +24,7 @@ export interface ParseConfig {
     /**
      * The parsing engine to use. Supported values:
      * * `parse_performance`: Full-featured parsing engine with highest accuracy (default)
-     * * `parse_light`: Lightweight parsing engine optimized for speed. This does not have robust layout support and does not support markdown layout target.
+     * * `parse_light`: Lightweight parsing engine optimized for high-volume, cost-sensitive ingestion. Uses the new layout model with full layout support and the markdown target at lower cost and latency, but performs worse than `parse_performance` on lower-quality scans, harder handwriting, larger tables, non-Latin-based languages, and dense checkbox regions.
      */
     engine?: Extend.ParseConfigEngine;
     /** Pin a specific parser engine version for reproducibility. When set to `latest`, the most recent stable version of the selected engine is used. */

package/api/types/ParseConfigBlockOptionsFigures.d.ts

@@ -8,4 +8,6 @@ export interface ParseConfigBlockOptionsFigures {
     figureImageClippingEnabled?: boolean;
     /** Whether to enable advanced chart extraction using vision models for improved data extraction from charts. */
     advancedChartExtractionEnabled?: boolean;
+    /** Custom instructions injected into the vision model prompt used to analyze and summarize figures. Use to steer figure descriptions toward your use case (e.g. domain terminology, details to always capture). Requires `enabled: true`. Available on `parse_performance` >= `2.0.0` and `parse_light` >= `1.0.0`. */
+    customInstructions?: string;
 }

package/api/types/ParseConfigEngine.d.ts

@@ -1,7 +1,7 @@
 /**
  * The parsing engine to use. Supported values:
  * * `parse_performance`: Full-featured parsing engine with highest accuracy (default)
- * * `parse_light`: Lightweight parsing engine optimized for speed. This does not have robust layout support and does not support markdown layout target.
+ * * `parse_light`: Lightweight parsing engine optimized for high-volume, cost-sensitive ingestion. Uses the new layout model with full layout support and the markdown target at lower cost and latency, but performs worse than `parse_performance` on lower-quality scans, harder handwriting, larger tables, non-Latin-based languages, and dense checkbox regions.
  */
 export declare const ParseConfigEngine: {
     readonly ParsePerformance: "parse_performance";

package/api/types/ParseConfigEngine.js

@@ -5,7 +5,7 @@ exports.ParseConfigEngine = void 0;
 /**
  * The parsing engine to use. Supported values:
  * * `parse_performance`: Full-featured parsing engine with highest accuracy (default)
- * * `parse_light`: Lightweight parsing engine optimized for speed. This does not have robust layout support and does not support markdown layout target.
+ * * `parse_light`: Lightweight parsing engine optimized for high-volume, cost-sensitive ingestion. Uses the new layout model with full layout support and the markdown target at lower cost and latency, but performs worse than `parse_performance` on lower-quality scans, harder handwriting, larger tables, non-Latin-based languages, and dense checkbox regions.
  */
 exports.ParseConfigEngine = {
     ParsePerformance: "parse_performance",

package/api/types/ParseConfigTarget.d.ts

@@ -11,7 +11,7 @@
  * * Prefer `markdown` for most documents, multi-column reading order, and retrieval use cases
  * * Prefer `spatial` for messy/scanned/handwritten or skewed documents, when you need near 1:1 layout fidelity, or for BOL-like logistics docs
  *
- * See “Markdown vs Spatial” in the [Parse guide](https://docs.extend.ai/2026-02-09/product/parsing/configuration-options#target-format) for details.
+ * See “Markdown vs Spatial” in the [Parse guide](https://docs.extend.ai/2026-02-09/parsing/configuration#target-format) for details.
  */
 export declare const ParseConfigTarget: {
     readonly Markdown: "markdown";

package/api/types/ParseConfigTarget.js

@@ -15,7 +15,7 @@ exports.ParseConfigTarget = void 0;
  * * Prefer `markdown` for most documents, multi-column reading order, and retrieval use cases
  * * Prefer `spatial` for messy/scanned/handwritten or skewed documents, when you need near 1:1 layout fidelity, or for BOL-like logistics docs
  *
- * See “Markdown vs Spatial” in the [Parse guide](https://docs.extend.ai/2026-02-09/product/parsing/configuration-options#target-format) for details.
+ * See “Markdown vs Spatial” in the [Parse guide](https://docs.extend.ai/2026-02-09/parsing/configuration#target-format) for details.
  */
 exports.ParseConfigTarget = {
     Markdown: "markdown",

package/api/types/ParseRun.d.ts

@@ -58,6 +58,12 @@ export interface ParseRun {
      * **Availability:** Present when `status` is `"FAILED"`.
      */
     failureMessage: string | null;
+    /**
+     * Any metadata that was provided when creating the parse run.
+     *
+     * **Availability:** Present when metadata was provided during creation.
+     */
+    metadata: Extend.RunMetadata | null;
     /**
      * The parse run output.
      *

package/api/types/ParseRunSummary.d.ts

@@ -0,0 +1,81 @@
+import type * as Extend from "../index";
+/**
+ * Summary representation of a parse run.
+ */
+export interface ParseRunSummary {
+    /** The type of object. Will always be `"parse_run"`. */
+    object: "parse_run";
+    /**
+     * A unique identifier for the parse run.
+     *
+     * Example: `"pr_xK9mLPqRtN3vS8wF5hB2cQ"`
+     */
+    id: string;
+    /**
+     * The ID of the batch this run belongs to, if created via `POST /parse_runs/batch`.
+     *
+     * **Availability:** Present when the run was submitted as part of a batch.
+     *
+     * Example: `"bpar_Xj8mK2pL9nR4vT7qY5wZ"`
+     */
+    batchId: string | null;
+    /** The file that was parsed. This file can be used as a parameter for other Extend endpoints, such as `POST /workflow_runs`. May be `null` for batch parse runs where file ingestion failed. */
+    file: Extend.FileSummary;
+    /**
+     * The status of the parse run:
+     * * `"PENDING"` - The run has been created and is waiting to be processed. Only applies to runs created via `POST /parse_runs/batch`.
+     * * `"PROCESSING"` - The file is still being processed
+     * * `"PROCESSED"` - The file was successfully processed
+     * * `"FAILED"` - The processing failed (see `failureReason` for details)
+     */
+    status: Extend.ParseRunSummaryStatus;
+    /**
+     * The reason for failure.
+     *
+     * **Availability:** Present when `status` is `"FAILED"`.
+     *
+     * Possible values include:
+     * * `UNABLE_TO_DOWNLOAD_FILE` - The file could not be downloaded from the provided URL
+     * * `FILE_TYPE_NOT_SUPPORTED` - The file type is not supported for parsing
+     * * `FILE_SIZE_TOO_LARGE` - The file exceeds the maximum allowed size
+     * * `CORRUPT_FILE` - The file appears to be corrupted or malformed
+     * * `OCR_ERROR` - An error occurred during optical character recognition
+     * * `PASSWORD_PROTECTED_FILE` - The file is password protected and cannot be processed
+     * * `FAILED_TO_CONVERT_TO_PDF` - The file could not be converted to PDF for processing
+     * * `FAILED_TO_CONVERT_TO_JPEG` - The file could not be converted to JPEG for processing
+     * * `FAILED_TO_GENERATE_TARGET_FORMAT` - The output could not be generated in the requested format
+     * * `CHUNKING_ERROR` - An error occurred while chunking the document
+     * * `INTERNAL_ERROR` - An unexpected internal error occurred
+     * * `INVALID_CONFIG_OPTIONS` - The provided configuration options are invalid
+     * * `OUT_OF_CREDITS` - Insufficient credits to process the file
+     *
+     * **Note:** Additional failure reasons may be added in the future. Your integration should handle unknown values gracefully.
+     */
+    failureReason: string | null;
+    /**
+     * A human-readable description of the failure.
+     *
+     * **Availability:** Present when `status` is `"FAILED"`.
+     */
+    failureMessage: string | null;
+    /**
+     * Any metadata that was provided when creating the parse run.
+     *
+     * **Availability:** Present when metadata was provided during creation.
+     */
+    metadata: Extend.RunMetadata | null;
+    /**
+     * Metrics about the parsing process.
+     *
+     * **Availability:** Present when `status` is `"PROCESSED"`.
+     */
+    metrics: Extend.ParseRunSummaryMetrics | null;
+    /**
+     * Usage credits consumed by this parse run. Omits `breakdown` — fetch the full parse run by id to see the per-line items.
+     *
+     * **Availability:** Present when `status` is `"PROCESSED"`, the run was created after October 7, 2025, and the customer is on the current billing system.
+     */
+    usage: Extend.RunUsageSummary | null;
+    createdAt: Extend.CreatedAt;
+    updatedAt: Extend.UpdatedAt;
+}

package/api/types/ParseRunSummary.js

@@ -0,0 +1,3 @@
+"use strict";
+// This file was auto-generated by Fern from our API Definition.
+Object.defineProperty(exports, "__esModule", { value: true });

package/api/types/ParseRunSummaryMetrics.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Metrics about the parsing process.
+ *
+ * **Availability:** Present when `status` is `"PROCESSED"`.
+ */
+export interface ParseRunSummaryMetrics {
+    /** The time taken to process the document in milliseconds. */
+    processingTimeMs: number;
+    /** The number of pages from the document that were parsed. For PDF and image files, this is the actual page count. For spreadsheet files (Excel, CSV), this is an estimated page count based on content volume (~1000 tokens per page). */
+    pageCount: number;
+}

package/api/types/ParseRunSummaryMetrics.js

@@ -0,0 +1,3 @@
+"use strict";
+// This file was auto-generated by Fern from our API Definition.
+Object.defineProperty(exports, "__esModule", { value: true });

package/api/types/ParseRunSummaryStatus.d.ts

@@ -0,0 +1,14 @@
+/**
+ * The status of the parse run:
+ * * `"PENDING"` - The run has been created and is waiting to be processed. Only applies to runs created via `POST /parse_runs/batch`.
+ * * `"PROCESSING"` - The file is still being processed
+ * * `"PROCESSED"` - The file was successfully processed
+ * * `"FAILED"` - The processing failed (see `failureReason` for details)
+ */
+export declare const ParseRunSummaryStatus: {
+    readonly Pending: "PENDING";
+    readonly Processing: "PROCESSING";
+    readonly Processed: "PROCESSED";
+    readonly Failed: "FAILED";
+};
+export type ParseRunSummaryStatus = (typeof ParseRunSummaryStatus)[keyof typeof ParseRunSummaryStatus] | string;

package/api/types/ParseRunSummaryStatus.js

@@ -0,0 +1,17 @@
+"use strict";
+// This file was auto-generated by Fern from our API Definition.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ParseRunSummaryStatus = void 0;
+/**
+ * The status of the parse run:
+ * * `"PENDING"` - The run has been created and is waiting to be processed. Only applies to runs created via `POST /parse_runs/batch`.
+ * * `"PROCESSING"` - The file is still being processed
+ * * `"PROCESSED"` - The file was successfully processed
+ * * `"FAILED"` - The processing failed (see `failureReason` for details)
+ */
+exports.ParseRunSummaryStatus = {
+    Pending: "PENDING",
+    Processing: "PROCESSING",
+    Processed: "PROCESSED",
+    Failed: "FAILED",
+};

package/api/types/ParseStepDefinition.d.ts

@@ -2,7 +2,7 @@ import type * as Extend from "../index";
 /**
  * Parses file content (OCR, text extraction). Every workflow should have exactly one parse step immediately after the trigger.
  *
- * See the [Parse step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#parse-step).
+ * See the [Parse step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#parse).
  */
 export interface ParseStepDefinition {
     name: string;

package/api/types/RuleValidationNextEntry.d.ts

@@ -2,7 +2,7 @@ import type * as Extend from "../index";
 /**
  * A next entry for `RULE_VALIDATION` steps. Routes based on whether all validation rules passed.
  *
- * See the [Configuring Workflows via API guide](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api) for end-to-end examples.
+ * See the [Configuring Workflows via API guide](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows) for end-to-end examples.
  */
 export interface RuleValidationNextEntry {
     /** The name of the target step. */

package/api/types/RuleValidationStepDefinition.d.ts

@@ -2,7 +2,7 @@ import type * as Extend from "../index";
 /**
  * Validates extraction outputs against formula-based rules. Routes to pass/fail next steps.
  *
- * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#rule-validation-step).
+ * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#rule-validation).
  */
 export interface RuleValidationStepDefinition {
     name: string;
@@ -11,7 +11,7 @@ export interface RuleValidationStepDefinition {
     /**
      * Can only be set when `config` is present. Each entry must include a `result` of `"pass"` or `"fail"` to route based on whether all validation rules passed.
      *
-     * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#rule-validation-step).
+     * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#rule-validation).
      */
     next?: Extend.RuleValidationNextEntry[];
 }

package/api/types/RuleValidationStepDefinitionConfig.d.ts

@@ -6,7 +6,7 @@ export interface RuleValidationStepDefinitionConfig {
     /**
      * Validation rules for this step. Each rule defines a name and a boolean formula.
      *
-     * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#rule-validation-step).
+     * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#rule-validation).
      */
     rules: Extend.RuleValidationStepDefinitionConfigRulesItem[];
 }

package/api/types/RuleValidationStepDefinitionConfigRulesItem.d.ts

@@ -3,7 +3,7 @@ export interface RuleValidationStepDefinitionConfigRulesItem {
     /**
      * Boolean formula used to validate the workflow data for this rule.
      *
-     * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/product/workflows/configuring-workflows-via-api#rule-validation-step) and [Formulas](https://docs.extend.ai/2026-02-09/product/workflows/formulas).
+     * See the [Rule Validation step docs](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows#rule-validation) and [Formulas](https://docs.extend.ai/2026-02-09/workflows/formulas).
      */
     formula: string;
     description?: string;

package/api/types/RunUsage.d.ts

@@ -6,7 +6,7 @@ import type * as Extend from "../index";
  * * Runs created before October 7, 2025
  * * Customers on legacy billing systems
  *
- * For more details on how credits work, see our [Credits Guide](https://docs.extend.ai/2026-02-09/product/general/how-credits-work).
+ * For more details on how credits work, see our [Credits Guide](https://docs.extend.ai/2026-02-09/general/how-credits-work).
  */
 export interface RunUsage {
     /** The credits consumed by this run. For most run types this is the line item for the run's own work; for `workflow_run` this is the aggregate across all child runs. */