Any file type.
One binary. Auto-detected.

CSV, images, video, PDF, audio, archives. The agent reads the content itself, figures out what it is, and picks the right way to process it. No format-specific extractors, no per-file config. One binary handles everything you throw at it.

Auto-detected → chunked
CSV / JSON / Parquetrow_range
Images (JPEG, PNG, WebP, GIF)file_per_chunk
Video (MP4, MOV, AVI, MKV)byte_range
PDF / Audiofile_per_chunk
Archives (ZIP, TAR, GZ)extract + recurse

Detected media
formats

The agent uses 10 format extractors to scan and classify every file by its actual content, not by extension.

format detection matrix
File TypeAuto-DetectsChunking StrategyUse Case
CSV / JSON / ParquetRows, columns, data types, headersrow_rangeTabular data, analytics pipelines, database exports
Images (JPEG, PNG, WebP, GIF)Format, dimensions, color depth, EXIF, face countfile_per_chunkImage classification, object detection, metadata extraction
Video (MP4, MOV, AVI, MKV)Container, codec, duration, resolution, keyframesbyte_range / file_per_chunkVideo transcoding, keyframe extraction, content moderation
PDFPage count, text content, embedded images, OCR textfile_per_chunkDocument processing, text extraction, form parsing
Audio (MP3, WAV, FLAC)Codec, sample rate, duration, channelsfile_per_chunkSpeech-to-text, audio classification, transcription pipelines
Archives (ZIP, TAR, GZ, 7Z)File listing, compression ratio, nested structureextract + recurseBatch processing, compressed data extraction, nested archives

How auto-detection
works

The agent doesn't guess file types from extensions. It reads the actual content.

  1. Content header scan

    When a file is added to a dataset, the agent reads the first few bytes to identify the file format, not the file extension. A .csv file mislabeled as .txt is still detected as CSV.

  2. Metadata extraction

    The format-specific extractor pulls relevant metadata: dimensions for images, codec and duration for video, page count for PDF, sample rate for audio, compression ratio for archives.

  3. Chunking strategy selection

    Based on format type and metadata, the agent selects the optimal chunking strategy. row_range for tabular, file_per_chunk for images/PDF/audio, byte_range for video, extract+recurse for archives.

  4. Plugin execution

    Each chunk is dispatched to the selected plugin via the embedded sandbox. The plugin receives the chunk data with format metadata. No format-specific config needed on the plugin side.

Mixed-format
pipelines

One agent handles every format in a single pipeline. No separate infrastructure per file type.

  1. E-commerce catalog enrichment

    Input: CSV product listings + product images + PDF spec sheets. Pipeline: extract CSV rows → resize images → extract PDF specs → merge enriched catalog. One agent, three formats, one pipeline.

  2. Medical imaging preprocessing

    Input: DICOM-style images + CSV metadata + PDF reports. Pipeline: extract image features → parse metadata → OCR reports → combine into structured output. All processed locally. Zero egress.

  3. Video content moderation

    Input: MP4 video files + JSON annotations. Pipeline: extract keyframes → run classification on frames → transcribe audio → merge results. One agent handles video, audio, and structured data.

SentraZero agent

One binary.
Every format.

CSV, images, video, PDF, audio. Everything runs through the same agent, the same sandbox, the same pipeline. No format-specific infrastructure to buy or maintain.