Comparison
| Pipeline | Speed | Accuracy | Best for |
|---|---|---|---|
cloudsquid-flash | Fastest | Good | High-volume, cost-sensitive, simple schemas |
cloudsquid-flash-v3 | Fast | Better | Default starting point — good balance of speed and quality |
cloudsquid-pro-v2 | Slower (10–30s) | High | Complex documents, nested schemas |
cloudsquid-pro-v3 | Slower | Highest | Dense or visually complex layouts, highest accuracy requirements |
Start with
cloudsquid-flash-v3 for all new tables. Switch to cloudsquid-pro-v3 only if accuracy on complex document layouts is insufficient.Bounding boxes
Enablingbounding_boxes adds source-location metadata to each extracted value — a reference back to the exact position in the original document. Useful for auditability and human review workflows, but increases processing time regardless of pipeline.
How to set a pipeline
Use the extraction settings endpoint to update a table’s active pipeline.Table Types
How Extraction, Reconcile, and Storage tables work together.
Async Run Pattern
The three-step upload → start → poll flow.
