Compliance & assurance · AVM
Controls & Oversight
Valtaic combines traceable API results with deployment checks, operational monitoring and rollback mechanisms. Customers use these controls alongside the review and decision policies for their own workflows.
Controls in the Valuation API
| Control | Behaviour |
|---|---|
| Traceable results | Responses carry release and execution identifiers, with a valuation identifier for each property result. |
| Explicit outcomes | Valued, referred, rejected and failed cases are distinguished, including individual batch rows. |
| Referral handling | Cases outside automated eligibility return a referral outcome, with the price withheld. |
| Input transparency | Applied stored values, ignored inputs and derived values are identified. |
| Uncertainty information | Available prediction ranges and confidence are returned as distinct signals. |
| Supporting evidence | Standard responses can include comparable transactions and location context. |
| Permissioned access | API keys, operation scopes and account limits govern access. |
| Version awareness | API contract versions and valuation releases are identified separately. |
Where asynchronous jobs are enabled, access is customer-scoped and jobs use the release accepted at submission. Check release metadata for the available capabilities.
Release Controls
The release process checks the valuation package, service readiness and representative responses before cutover. Contract, authentication, permission and outcome-handling tests help detect serving regressions.
Deployment checks retain the previous service during qualification and support rollback if a cutover fails. These checks verify serving behaviour; accuracy evaluation has its own scope, described in Performance & Validation.
Keep the release identifier with the original request, response, timestamp and returned identifiers. Serving software can change while the valuation release remains the same.
Performance and Operational Monitoring
Operational monitoring covers service health, server errors, response times, resource pressure and job-queue age. Alerts support investigation of failures and capacity pressure.
Accuracy assessment examines valuation outcomes and the properties being valued. Internal segmented and behavioural analysis supports investigation. Diagnostic findings and enforced deployment checks have different roles in release decisions.
For your deployment, agree monitoring frequency, accountable contacts, escalation thresholds and actions when results or service conditions change. Contractual availability and response arrangements are set in the service terms.
Human Oversight
Customers establish acceptance criteria and arrange human review for referred, uncertain or disputed cases unless a separate service has been agreed. Specify who reviews the case, what evidence they receive, and how their decision or override is recorded.
Preserve the automated result alongside any subsequent professional assessment. This keeps the distinction between the API estimate and the customer's final decision clear.
Records and Change Control
Retain the request and response, valuation date, timestamp and returned identifiers, plus row and job identifiers where relevant. Record a refreshed valuation as a new observation and apply your access and retention rules.
Review representative cases after material releases, changes to the target property population or changes in intended use. Document decisions to continue, restrict or pause reliance. See Versioning and Releases.
For deployment questions or an issue requiring investigation, contact hello@valtaic.io with the relevant identifiers and a description of the behaviour. Keep credentials and unnecessary personal information out of support correspondence.