Docs · Validators

`number_range` validator

Coerce to a finite number and bound it between optional min/max.

Get an API key Read the docs

One of 19 validator types · pure compute, no AI cost

Reference

Format

Coerced with `Number(value)` and rejected if not `Number.isFinite`. Bounds are inclusive numerical comparisons.

Examples

min: 0, max: 100 // percentages
min: 0 // non-negative quantities
min: -273.15 // temperatures

How it runs

Implementation

A faithful summary of lib/validators.ts. Validators are pure functions and run identically in the Worker, the Workbench and the MCP server — one implementation, so the three cannot disagree about whether a value is valid.

lib/validators.ts

function validNumberRange(value, params) {
  const n = Number(value)
  if (!Number.isFinite(n)) return fail('number_invalid', 'not a number')
  if (params.min != null && n < params.min) return fail('number_too_small', `< ${params.min}`)
  if (params.max != null && n > params.max) return fail('number_too_large', `> ${params.max}`)
  return OK
}

Config

Use in a template

Validators attach to a field on a custom template. The cascade runs them after mapping but before commit; failures surface in the per-row validation report.

template.yaml

fields:
  - column: deal_score
    type: number
    validators:
      - type: number_range
        min: 0
        max: 100

Watch out

Common gotchas

Empty string coerces to 0 in JavaScript — but the upstream "empty bypass" rule means blanks skip validation entirely. `"0"` is valid; `""` is skipped.
Locale-formatted numbers (`"1,234.56"` or `"1.234,56"`) become NaN. Normalize in your transform.
Bounds are inclusive — `min: 0` accepts `0`.

Where it runs

Three routes, no AI cost.

POST/v1/validate-rowValidate one row against a template. Stateless, no key, pure compute — the fastest way to try number_range against a real value.no key
POST/v1/uploads/:id/validateRun every field validator over the parsed upload, without committing. Returns errors and warnings per row.read
POST/v1/uploads/:id/commitValidates on the way out. skip_invalid_rows drops the failures instead of failing the commit.commit

Validators are pure functions, so they add nothing to the AI bill. Every map draws a small flat per-map fee from your prepaid token wallet ($10 minimum, shared across the phi-cloud suite); only columns that reach the metered LLM layer, plus any-to-any convert and structural reshape, bill real AI tokens. See pricing

Catalogue

Related templates

Opportunitiesopportunities_v1
Deals in pipeline: amount, stage, probability, close date, owner.
Fields · probability

Explore

All 19 validator types

The complete list a template field can declare. There is no SNOMED validator — it required an affiliate licence, no template used it, and it was removed in 2026.

Back to the documentation index or browse the template catalogue.

Ready when you are

Validate every row — before it lands.

Attach checksum-strict validators to any field, and gate risky commits behind the requires_hitl flag. One key runs the whole cascade.

Get an API key See pricing

Prepaid token wallet · schema-only data-minimization mode · no free tier

number_range validator