Where the product is today

  • Today, supported invoice, named-field and table extraction use deterministic rules over native text or local OCR.
  • Customer model selectors, provider routing and model spending controls are not available in the current trial.

An unfamiliar statement layout

A future route could use an approved extraction rule for a known layout and request model assistance for an unfamiliar one. Both paths would face the same evidence and balance checks; unresolved results would go to review instead of triggering unlimited retries.

Availability and evaluation

  • No model provider, gateway, model list or token price is promised by this roadmap.
  • A cheaper model can increase correction effort. Selection needs measured accepted-outcome cost, not token price alone.
  • Provider fallback must preserve the required capabilities and data-handling policy; an unsupported route should stop visibly.
  • Routing cannot guarantee a correct answer, and model confidence alone cannot approve a business record.

What we plan to build

  • Describe task requirements, supported inputs, output contracts and data-handling constraints before selecting a provider or model.
  • Support a provider-neutral adapter and evaluate direct provider access, approved routing gateways and suitable local models.
  • Choose an evaluated deterministic path first for known inputs; escalate novel or unresolved cases to an appropriate model or reviewer.
  • Use capable models to help discover new procedures without requiring a frontier model on every routine run.
  • Reserve per-step and per-workflow budgets, cap retries, and record actual model, provider, usage and fallback reasons.
  • Let customers choose evaluated quality, latency and spending policies while preserving mandatory review and data constraints.

How this should be evaluated

  • Compare candidates on held-out tasks, including invalid output, missing evidence and refusals.
  • Measure cost per accepted result with retries, human correction and failure handling included.
  • Test provider outages, budget exhaustion and fallback routes that cannot meet the required contract.
  • Record the resolved model and configuration so a routing or model change can be evaluated separately.