Nested Task Options
Task-specific configuration is now nested inside an options object.
What changed
Previously, task options were mixed with top-level fields:
Now, options are nested:
Quality is now a string enum
Quality values changed from numeric (1-100) to a string enum for consistency:
very_low, low, medium, high, very_high
Task inputs and outputs are arrays
Task responses now use inputs and outputs (arrays) instead of singular input and output objects.
api
2025-10-20