r-1 is currently in preview and requires the V3 API. API requests use legacy Parse unless they set
settings.model to "r-1". New pipelines in Studio use r-1 by default.Enable r-1
Setsettings.model to "r-1" on a V3 Parse request. A request that omits settings.model runs on legacy Parse.
How r-1 compares with legacy Parse
r-1 replaces the general-purpose use of agentic text, table, and figure scopes. You can combine r-1 with agentic processing when your workflow needs one or more custom prompts or a specialized augmentation. Reducto runs the relevant agentic components and augments the r-1 result.
What r-1 handles natively
Augment r-1 with customized agentic processing
r-1 handles the document structures that previously required general-purpose agentic processing. Add customized agentic processing when your workflow needs a custom prompt or advanced chart extraction. For example, a table prompt can tell Reducto how to encode domain-specific content in the parsed output. Theagentic array can include custom prompts for more than one supported scope. Pages that need a custom prompt run through the matching agentic pipeline, while other pages continue through r-1. Agentic processing adds latency.
For structured chart data, add advanced chart extraction to a figure-scoped agentic configuration. Reducto runs the separate chart extraction agent and augments the r-1 result.
Check configuration compatibility
Review supported, ignored, and unsupported settings before migrating an existing Parse configuration.
Parse overview
Run Parse and review the main request and response structure.
Parse configurations
Configure chunking, formatting, retrieval, and processing settings.