app icon
xParse
1.0.0

xParse is a modern AI infrastructure for document processing, built for RAG and agentic workflows on LLMs.

intsig-textin/xparse312 installs

xParse Document Parsing Tool

Author: intsig-textin
Version: 0.0.1
Type: tool


Description

xParse Document Parsing Tool extracts structured content from various file formats (PDF, WORD, EXCEL, PPT, images, etc.) and converts them into queryable and analyzable structured elements.


Provider Credentials

When configuring the plugin in Dify, you need to provide the following credentials:

Get your credentials: Please log in to Textin and go to Workspace → Account Settings → Developer Information to view your and .

ParameterTypeRequiredDescription
secret-inputYesTextin application ID. Please log in to Textin and go to "Workspace → Account Settings → Developer Information" to view x-ti-app-id. See API Documentation for details.
secret-inputYesTextin secret code. Please log in to Textin and go to "Workspace → Account Settings → Developer Information" to view x-ti-secret-code. See API Documentation for details.

Parse Input Parameters

The xParse Parse tool provides parameters to customize the processing of documents.

The only required parameter is – the file you wish to process.


Main Parameters

ParameterTypeRequiredDefaultDescription
fileYes-The file to be parsed (supports PDF, WORD, EXCEL, PPT, images, etc.)
selectNoThe document parsing provider/engine to use. Options: (Recommended), , ,
stringNo-Password for encrypted PDF files
stringNo-Specify page ranges to parse. Format: for page 15, for pages 20-25, for pages 1, 3, 5, 6, 7
selectNoWhether to perform crop and dewarp preprocessing. Options: (No), (Yes)
selectNoWhether to remove watermark preprocessing. Options: (No), (Yes)
booleanNoWhether to return page images (for PDF and other formats that need to be converted to images)
booleanNoWhether to return sub-images within pages

TextIn Engine Specific Parameters

The following parameters only apply when is set to :

ParameterTypeRequiredDefaultDescription
selectNoPDF parsing mode. Options: (extract text directly from PDF), (treat PDF as images). Note: Images always use scan mode
selectNoControl underline recognition range (only for scan mode). Options: (No recognition), (Only recognize underlines without text)
selectNoWhether to enable chart recognition. Recognized charts will be output as tables. Options: (No), (Yes)

Advanced Parameters

ParameterTypeRequiredDefaultDescription
stringNo-JSON format S3 storage configuration for storing page images. Includes: , , , , , ,

Notes

  • For more details on each parameter, refer to the xParse Parse Documentation.
  • Some parameters are only available for specific providers or file types.
  • Default values are shown where applicable.

API Response Structure

Top-Level Fields

The tool returns structured data with the following fields:

FieldTypeDescription
stringThe full parsed content in Markdown format, including images, sections, etc.
array of objectList of structured content blocks (sections, paragraphs, images, tables, etc.)
array of objectList of image objects extracted from the content (if or is enabled)

Field Details

text

  • Type: string
  • Description:
    The entire content, formatted in Markdown. This includes images (as markdown image syntax), headings, paragraphs, and other formatting for direct rendering.

elements

  • Type: array of objects
  • Description:
    List of structured content blocks. Each object represents a section, paragraph, image, table, or other content element extracted from the document.

Each element object contains:

FieldTypeDescription
stringUnique identifier for the element (SHA-256 hash of text + coordinates + page number + filename)
stringThe type of element (e.g., , , , , )
stringThe text content of the element
objectMetadata for the element (see below for details)
metadata (object)

The field provides detailed information about the element's origin, layout, and context.

Common fields include:

FieldTypeDescription
stringName of the source file (e.g., )
stringMIME type or file type (e.g., )
stringTimestamp of last file modification
integerPage number in the source file (if applicable)
integerWidth of the page in pixels
integerHeight of the page in pixels
array8-element array representing quadrilateral coordinates (normalized, range [0, 1])
stringID of the parent element
integerDepth in the document hierarchy
stringBase64 encoded image data (if is enabled)
stringMIME type for images (e.g., )
stringURL for page image (if is enabled)
stringURL for original page image (if preprocessing is enabled)
stringPreview URL for images (after uploading to Dify)
stringUnique file ID for images in Dify
stringHTML representation for tables or rich text elements
objectData source information including record locator, URLs, version, dates

images

  • Type: array of objects
  • Description:
    List of images found in the content (only returned if or is enabled). Each image object contains:
FieldTypeDescription
stringUnique image ID (Dify file ID)
stringImage file name
stringMIME type of the image
stringURL for image preview
integerImage file size in bytes
stringAlways

Example Response

JSON Structure


Usage

  1. Install this plugin in Dify
  2. Configure Provider credentials ( and )
  3. Use the Parse tool in Workflow or Agent applications
  4. Upload a file and configure parsing parameters
  5. Get parsed structured content and images

API Reference


Notes

  • The field is suitable for direct display in web or app frontends.
  • The field is useful for structured processing, highlighting, or further analysis.
  • The field provides all image resources for preview or download.
  • The object in each element may contain additional fields depending on the extraction process and file type.
  • Image processing:
    • When is enabled, images () are automatically decoded and uploaded to Dify's file system. Their and are included in the response , and images are added to the list.
    • When is enabled, page image URLs () are directly included in the response and are not uploaded to Dify's file system.
CATEGORY
Tool
VERSION
1.0.0
intsig-textin·02/04/2026 02:15 PM
REQUIREMENTS
Tool invocation
App invocation
Endpoint registration
Maximum memory
256MB
Maximum storage
1MB