A
AI Capability Platform — the engine layer that transforms raw observations into structured intelligence through specialised AI engines.
AAMOS (Adaptive Autonomous Multi-Observation System) is not a single AI system — it is a platform of composable AI engines. Each engine handles a specific domain: Vision for object detection, Identity for verification, Fraud for anomaly detection, Infrastructure for asset condition, and more. Developers access AAMOS through REST APIs that accept images, video, or structured data and return verified intelligence. AAMOS is developed and sold by Landvex Inc, Houston, TX — there is no "AAMOS Group."
In the ecosystem
A municipality uploads 10,000 bridge photos to AAMOS Infrastructure. The engine detects cracking, corrosion, and structural anomalies, scoring each asset by severity. The output feeds directly into Landvex's Infrastructure Risk Index.
The end-to-end process for training, validating, and deploying computer vision models across AAMOS engines.
The AAMOS training pipeline ingests labelled datasets (from SceneNet, ContribNet, and verified field observations), trains models using YOLO and other architectures, validates against hold-out test sets, and exports production-ready ONNX models. The pipeline includes automated data augmentation, hyperparameter tuning, and model drift detection. Every deployed model carries a version tag and confidence calibration curve.
In AAMOS
A new facade-damage model is trained on 50,000 labelled images from ContribNet. After validation achieves 94% mAP, it is exported to ONNX and deployed to the Infrastructure Engine with a calibrated confidence threshold of 0.72.
Application Programming Interface — the programmatic interface through which developers access AAMOS engine capabilities.
The AAMOS API is a REST-style HTTP API that exposes all engine capabilities as standardised endpoints. Authentication uses OAuth 2.0. Responses are JSON with structured confidence scores, bounding boxes, and provenance metadata. Webhooks deliver asynchronous results for batch operations. Rate limits and usage quotas are enforced per API key.
In AAMOS
An insurance platform integrates the AAMOS Fraud API. When a claim photo is uploaded, a POST to /detect returns object annotations, damage severity scores, and manipulation flags within 800ms — enabling real-time claims triage.
AI engine for regulatory compliance checks, documentation verification, and standard adherence detection.
AMOS Compliance analyses visual and document evidence against regulatory frameworks: safety signage requirements, accessibility standards, environmental permits, and building codes. It identifies missing elements, non-conforming installations, and documentation gaps. Outputs include compliance scores, violation lists with regulatory references, and remediation priorities.
In AAMOS
A construction site photo is analysed by AMOS Compliance. The engine detects missing hard-hat signage, an uncovered trench without barriers, and a fire extinguisher past inspection date — each flagged with the specific OSHA clause violated.
AI engine for detecting visual fraud: skimming devices, manipulated meters, forged documents, and insurance scams.
AMOS Fraud applies computer vision and document analysis to detect tampering, overlays, and anomalous modifications in physical assets and documents. It identifies ATM skimmers by comparing against reference images, detects manipulated utility meters through seal verification, and flags forged identity documents via microprint and font analysis. Each finding includes a fraud probability score and recommended action.
In AAMOS
A bank submits daily ATM photos to AMOS Fraud. The engine flags one machine with a 97% fraud probability — a card reader overlay detected through dimensional analysis and texture inconsistency. The alert triggers immediate lockdown before any customer data is compromised.
AI engine for identity verification, document authentication, liveness detection, and facial comparison.
AMOS Identity verifies that a person is who they claim to be. It analyses government-issued IDs for forgery indicators, performs liveness checks to prevent spoofing (photos, masks, replay attacks), and compares facial biometrics against the ID photo. The engine outputs a verification confidence score, spoof probability, and document authenticity rating. It powers KYC flows for quiXzoom and enterprise customer onboarding.
In AAMOS
A Zoomer completes KYC via the quiXzoom app. AMOS Identity analyses their passport photo, performs a liveness challenge (blink, turn head), and compares the live face against the document — all in under 10 seconds with 99.2% confidence.
AI engine for analysing roads, bridges, buildings, poles, signs, and other physical infrastructure assets.
AMOS Infrastructure ingests visual observations of built assets and outputs condition assessments: crack detection, corrosion scoring, vegetation encroachment, signage legibility, and structural anomaly flags. It compares current observations against historical baselines to detect change and deterioration trends. Outputs include per-asset condition indices, maintenance priority rankings, and georeferenced anomaly maps.
In AAMOS
A county uploads 5,000 road segment observations. AMOS Infrastructure detects 312 potholes, 47 cracked culverts, and 23 faded road markings — each geotagged, severity-scored, and mapped for maintenance crew dispatch.
General-purpose AI engine for quality control, industrial inspection, and defect detection across manufacturing and logistics.
AMOS Inspection applies computer vision to quality assurance scenarios: surface defect detection on production lines, packaging integrity verification, assembly completeness checks, and logistics damage assessment. Unlike Infrastructure (which focuses on civil assets), Inspection handles manufactured goods, equipment, and industrial processes. It integrates with conveyor systems, drone feeds, and handheld inspection devices.
In AAMOS
A manufacturer feeds conveyor-belt camera streams to AMOS Inspection. The engine detects paint scratches, dimensional deviations, and missing components in real time — rejecting 0.3% of units with 99.7% accuracy, reducing manual QC headcount by 60%.
AI engine for detecting PPE compliance, workplace hazards, and safety protocol violations.
AMOS Safety analyses visual feeds from construction sites, factories, and field operations to identify safety risks: missing hard hats, unguarded machinery, blocked emergency exits, improper ladder use, and chemical storage violations. It generates real-time alerts for immediate intervention and compiles safety scorecards for management review. The engine learns site-specific safety protocols and adapts detection rules per environment.
In AAMOS
A construction site safety officer receives an alert: AMOS Safety detected a worker without a harness at height in Zone B. The alert includes a timestamped photo, GPS location, and worker ID (if visible). Response time from detection to alert: 3.2 seconds.
Core AI engine for object recognition, anomaly detection, and damage classification in visual data.
AMOS Vision is the foundational computer vision engine powering all other AAMOS modules. It performs object detection (YOLO-based), instance segmentation, image classification, and anomaly detection on visual inputs. The engine runs on ONNX-exported models for cross-platform deployment (cloud, edge, mobile). It is the first processing layer for every visual observation entering the AAMOS pipeline.
In AAMOS
A drone captures aerial imagery of a solar farm. AMOS Vision detects 12 panels with hot-spot anomalies, 3 with physical cracks, and flags one inverter housing with corrosion — all in a single pass, processed in 2.1 seconds per image.
API endpoint that verifies identity by comparing a live capture against a trusted reference (ID photo, enrolled biometric).
The /authenticate endpoint accepts a live image or video stream and a reference image (e.g., passport photo, previously enrolled face), then returns a match confidence score, liveness verification result, and spoof detection flag. It is the core of identity verification flows and access control systems. The endpoint supports 1:1 comparison only; for 1:N identification, use /identify.
API Usage
POST /authenticate with {reference_image: "base64...", capture: "base64...", challenge_type: "blink"} returns {match_confidence: 0.987, liveness_passed: true, spoof_probability: 0.002}.
AMOS Vision Orchestrator — real-time guidance system that directs field capture to ensure sufficient evidence quality.
AVO is an orchestration layer that guides field data collection through two phases: Phase A (live guidance) provides real-time feedback to the capture device — "move closer," "adjust angle," "increase lighting" — ensuring the captured media meets quality thresholds before submission. Phase B (post-capture) validates that the submitted evidence satisfies the verified_claim requirements for the specific knowledge pack (vehicle_wheel, building_facade, passport, etc.). AVO is the bridge between raw capture and verified evidence.
In quiXzoom
A Zoomer photographs a building facade. AVO Phase A guides them: "Step back 2 metres," "Centre the entrance," "Wait for shadow to pass." After capture, AVO Phase B confirms the image contains sufficient detail for crack detection — trust_achieved = 0.91, exceeding the 0.85 threshold.
C
AMOS engine that detects differences between current observations and historical baseline data — surfacing what has changed in the physical world.
The Change Engine compares new observations against prior data to identify additions, removals, or modifications to physical assets. It operates at multiple scales: pixel-level differences in repeated photographs, structural changes through computer vision, and semantic changes (e.g., "this was a parking lot, now it's construction"). Each detected change is scored by confidence and severity, and flagged as a Contradiction when it represents an unexpected deviation. The Change Engine powers infrastructure monitoring, property condition tracking, and environmental surveillance.
In AAMOS
A quarterly observation of a retail park shows three new storefronts and one demolished unit compared to the baseline from six months ago. The Change Engine automatically flags these modifications, updates the asset registry, and alerts the property manager.
API endpoint that categorises an image or object into predefined classes with confidence scores.
The /classify endpoint assigns input media to one or more categories from a trained taxonomy. Unlike /detect (which finds objects), /classify answers "what is this?" for the entire input. It supports multi-label classification (an image can belong to multiple classes) and hierarchical taxonomies (e.g., Vehicle → Car → Sedan). Confidence scores are calibrated and include an "unknown" class for inputs that don't match any trained category.
API Usage
POST /classify with {image: "base64...", taxonomy: "infrastructure_damage"} returns {classes: [{label: "crack", confidence: 0.94}, {label: "spalling", confidence: 0.71}], top_class: "crack"}.
API endpoint that analyses two images of the same asset and reports differences, similarities, and change severity.
The /compare endpoint is the programmatic interface to the Change Engine. It accepts a baseline image and a current image (plus optional GPS and timestamp metadata), aligns them geometrically, and outputs a structured change report: added elements, removed elements, modified regions, severity scores per change, and an overall change index. It is used for automated condition monitoring, insurance claims validation, and regulatory compliance verification.
API Usage
POST /compare with {baseline: "base64...", current: "base64...", asset_id: "BR-2847"} returns {changes: 3, severity: "moderate", details: [...], change_index: 0.34}.
Descriptive intelligence that tells you the current state of your physical assets — what is, not what to do.
Control Intelligence answers the question: "What is the current condition of my assets?" It is the foundational layer of insight derived from observations, describing reality as it exists today: which bridges are sound, which buildings have damage, which roads need repair. Control Intelligence is objective, measurable, and verifiable. It is the raw material from which Decision Intelligence is forged — you cannot decide what to do until you know what is. Landvex delivers Control Intelligence as indices, scores, and contradiction flags.
In Landvex
A municipality receives Control Intelligence showing that 12% of its road bridges have surface cracking, 3% have structural concerns, and 85% are in good condition. This descriptive baseline is the starting point for all maintenance and investment decisions.
A geographic visualisation showing where quiXzoom observations have been collected, updated, and verified.
The Coverage Map displays observation density, freshness, and quality across geographic regions. It answers the critical question for PBOI customers: "How complete is my data?" Coverage is expressed as a percentage of target assets observed within a defined polygon, with colour-coding by refresh SLA compliance. Green = observed within SLA, Yellow = approaching expiry, Red = stale or missing. Coverage Maps are a core component of Landvex subscription offerings.
In Landvex
A property manager views the Coverage Map for their retail portfolio: 94% of storefronts have observations within 30 days, 4% are approaching refresh, and 2% have no recent data. They order targeted missions for the red zones.
L
Control Intelligence company operating through Landvex AB (EU) and Landvex Inc. (US) — the decision layer of the ecosystem.
Landvex combines field-verified intelligence from quiXzoom, AI-driven analysis from AAMOS, and cross-market operational coverage through its European and North American entities. The Landvex platform enables infrastructure owners, governments, utilities, and enterprises to identify risks, opportunities, deficiencies, and emerging conditions before they become operational problems. Landvex does not sell AI — it sells intelligence based on AMOS engines. Key products: VIMS, Reality Alerts, RIOS, and Control Intelligence APIs.
In the ecosystem
quiXzoom collects 12,000 observations of bridge conditions across Sweden. AMOS processes these into condition scores. Landvex aggregates them into an Infrastructure Risk Index, adds historical trends and environmental data, and delivers a prioritised maintenance plan to the county — complete with cost estimates and confidence intervals.
The verification that a captured biometric (face, fingerprint) comes from a live person, not a photo, mask, or replay.
Liveness detection prevents spoofing attacks in identity verification. AAMOS Identity uses multiple liveness signals: challenge-response (blink, turn head, smile), texture analysis (detecting screen glare, paper edges, or mask seams), depth estimation (3D face geometry), and temporal consistency (natural micro-movements). A liveness score above the threshold is required for authentication to proceed. Liveness is critical for KYC, access control, and fraud prevention.
In AAMOS
A fraudster attempts to verify using a high-quality printed photo of a passport holder. AMOS Identity's liveness detection flags the attempt: texture analysis detects paper fibre patterns, depth estimation shows flat geometry, and the challenge-response fails (no natural blink). Spoof probability: 0.97. Verification denied.
O
The authentication protocol used by the AAMOS API — industry-standard delegated access without sharing passwords.
AAMOS uses OAuth 2.0 with bearer tokens for API authentication. Developers register applications to receive client credentials, then exchange them for short-lived access tokens. Refresh tokens enable long-lived integrations without storing passwords. Scopes control which engines and endpoints an application can access. OAuth 2.0 is the same protocol used by Google, GitHub, and Stripe.
A verified field record captured through quiXzoom — the fundamental unit of reality data.
An observation is a structured, verified record of physical reality at a specific place and time. Every observation includes: geolocation (GPS coordinates with accuracy estimate), timestamp (when captured), media (images or video), and metadata (device, conditions, mission context). Observations are quality-checked by AI before entering the dataset. They are the raw material from which all Landvex intelligence is derived.
In quiXzoom
A Zoomer captures 6 images of a road segment. Each image becomes part of an observation that includes GPS, timestamp, and mission context. AI review verifies the observation before it enters the dataset.
Open Neural Network Exchange — the standard format for AAMOS model deployment, enabling cross-platform inference.
ONNX is an open standard for representing machine learning models. AAMOS trains models in PyTorch, then exports to ONNX for deployment. ONNX models run on multiple backends: NVIDIA GPUs (via TensorRT), Intel CPUs (via OpenVINO), mobile devices (via ONNX Runtime), and cloud instances. This flexibility allows AAMOS to deploy the same model to edge devices (quiXzoom app), on-premise servers (enterprise customers), and cloud infrastructure (high-throughput API) without retraining.
In AAMOS
A new crack-detection model is trained in PyTorch, validated at 94% mAP, exported to ONNX, and deployed simultaneously to: (1) the cloud API for batch processing, (2) an edge device for real-time construction site monitoring, and (3) the quiXzoom app for offline AVO guidance.
Q
The internal currency unit of the quiXzoom platform, used for mission pricing, Zoomer compensation, and platform accounting.
QX Credits are quiXzoom's internal accounting unit. All mission prices, Zoomer earnings, and platform transactions are denominated in QX Credits. 1 QX Credit = 1 USD (fixed exchange rate, no speculation). QX Credits provide a stable, platform-native unit of account that simplifies global operations — Zoomers in any country earn QX Credits, which are converted to their local currency at payout via Stripe Connect. Orderers purchase QX Credit packages to fund missions.
In quiXzoom
A mission pays 8.0 QX Credits. A Zoomer in Thailand completes and gets approval — their account is credited 8.0 QX. At Monday payout, Stripe Connect converts 8.0 USD to THB at the day's exchange rate and deposits to their Thai bank account.
Blockchain-tracked token representing earned value on the quiXzoom platform — immutable, auditable, and non-speculative.
The QZ Token is a blockchain-based representation of quiXzoom earnings. Each token is created when a mission is approved and stored on an immutable ledger. The ledger provides complete auditability: every token's origin (which mission, which Zoomer, which timestamp), transfer history, and redemption record is permanently recorded. QZ Tokens are NOT a cryptocurrency for trading — they are an accounting and transparency mechanism. 1 QZ Token = 1 USD = 1 QX Credit.
In quiXzoom
A Zoomer completes 50 missions in a month, earning 420 QZ Tokens. The blockchain ledger records each token's provenance: mission ID, approval timestamp, AI review score, and payout transaction hash. An auditor can trace every token from mission creation to bank deposit.
Field Intelligence Network — the global crowdsourced data collection platform that feeds the Landvex ecosystem.
quiXzoom is a marketplace where orderers (customers) post data collection missions and Zoomers (verified field contributors) complete them for compensation. It is a standalone product and brand, not a module of AAMOS. quiXzoom uses AAMOS engines under the hood for AI review and quality control, but presents itself as an independent field intelligence platform. quiXzoom's purpose is to collect verified, geotagged, timestamped observations of physical reality at global scale.
In the ecosystem
quiXzoom collects 50,000 observations per month across 12 countries. These feed into AAMOS for analysis and Landvex for intelligence products. The same Zoomer, app, and infrastructure serve both commercial (SME) and enterprise (government) customers.
R
Unprocessed visual captures from field operations — the input state before AI review, geotag validation, or structured packaging.
Raw Data refers to the initial media files captured by Zoomers before any processing: the original JPEG/HEIC from the camera, with native EXIF, before AI review, before quality scoring, before packaging into an observation. Raw Data is retained for a limited period for dispute resolution and audit purposes, then purged according to the data retention policy. Customers never receive Raw Data — they receive processed, verified observations.
Real-time notifications triggered when AAMOS detects significant changes, contradictions, or anomalies in monitored assets.
Reality Alerts are Landvex's proactive notification system. When the Change Engine or Risk Engine detects a condition that exceeds a customer's configured threshold, a Reality Alert is generated and delivered via webhook, email, SMS, or in-app notification. Alert types include: Contradiction Alert (unexpected change detected), Risk Escalation (index crossed a threshold), Coverage Gap (area hasn't been observed within SLA), and Opportunity Signal (PBOI lead identified). Each alert includes the evidence, confidence score, recommended action, and a link to the full analysis.
In Landvex
A property manager receives a Reality Alert: "Contradiction detected at Property 2847. New water staining on north facade not present in baseline (6 months ago). Risk Index elevated from 34 to 67. Recommended action: schedule inspection within 14 days." The alert includes the before/after comparison and the observation photo.
AMOS engine that verifies an image shows actual reality — not a manipulated, synthetic, or replayed scene.
The Reality Engine is AAMOS's first line of defence against fraudulent or manipulated inputs. It analyses images for signs of tampering: inconsistent lighting, unnatural shadows, compression artefacts at edit boundaries, cloned regions, and AI-generated content (deepfakes). It also verifies EXIF integrity, GPS consistency, and timestamp plausibility. The Reality Engine does not determine what the image shows — it determines whether the image is trustworthy. A failed Reality Engine check blocks the observation from entering downstream analysis.
In AAMOS
A claim photo is submitted showing severe flood damage. The Reality Engine flags it: EXIF timestamp predates the flood event by 3 days, GPS coordinates are 200km from the claimed location, and shadow analysis suggests the photo was taken under different lighting conditions than reported. The observation is quarantined for manual review.
The measurable difference between reported or planned reality and observed reality — Landvex's core detection target.
The Reality Gap is the space between what should be and what is. It manifests as: infrastructure that is reported maintained but observed deteriorated, buildings that are permitted as safe but show structural concerns, or urban plans that describe green spaces but deliver concrete. Landvex's Contradiction Analysis systematically identifies Reality Gaps by comparing official records, design specifications, and historical baselines against current observations. The Reality Gap Index (RGI) quantifies this gap per asset or region.
In Landvex
A municipality's asset register shows Bridge 2847 as "good condition, last inspected 2024." Landvex observations reveal active crack propagation and spalling. The Reality Gap is flagged: reported condition ≠ observed condition. The Contradiction triggers a Reality Alert and updates the Infrastructure Risk Index.
A measurable, verifiable observation that describes a specific aspect of the physical world.
A Reality Signal is any observation that carries information about the state of physical reality: a photo of a cracked bridge deck, a GPS-tagged image of flood damage, a timestamped record of a building's facade. Reality Signals are distinguished from synthetic or inferred data by their direct connection to physical measurement — a Zoomer was there, the camera captured light from the actual scene, the GPS recorded the actual coordinates. Reality Signals are the antidote to assumptions and desk-based estimates.
In quiXzoom
An insurer receives a Reality Signal showing hail damage to a factory roof — captured 6 hours after the storm, with GPS confirming the location, timestamp proving immediacy, and image quality enabling damage severity assessment. This Reality Signal replaces the traditional adjuster visit.
Service Level Agreement governing how frequently observations must be updated to remain current — a core component of PBOI subscriptions.
The Refresh SLA defines the maximum age of observations for a given asset class and geographic area. Different asset types have different refresh requirements: dirty storefront windows need weekly refresh (conditions change fast), while building facades can be quarterly (deterioration is slower). The Coverage Map visualises SLA compliance: green = within SLA, yellow = approaching expiry, red = stale. Refresh SLA is a contractual commitment in Landvex subscription agreements.
In Landvex
A retail chain's PBOI subscription specifies: storefront windows = 7-day refresh, parking lots = 14-day, building exteriors = 90-day. The Coverage Map shows 96% compliance for windows, 89% for parking, and 94% for exteriors. Landvex schedules batch missions for the non-compliant zones.
Reality Intelligence Operating System — Landvex's platform for orchestrating data collection, analysis, and decision delivery.
RIOS is the operating system that coordinates the entire Landvex intelligence pipeline. It manages: mission scheduling and dispatch to quiXzoom, data ingestion from field operations, AMOS engine orchestration, index computation, alert generation, and customer dashboard delivery. RIOS is not a product sold separately — it is the infrastructure that powers all Landvex intelligence products. Think of it as the "OS" that runs on top of the quiXzoom + AAMOS stack.
In Landvex
A municipal customer subscribes to Infrastructure Intelligence. RIOS automatically schedules quarterly observation missions via quiXzoom, routes the results through AMOS Infrastructure, computes Infrastructure Risk Index updates, generates Reality Alerts for anomalies, and delivers a monthly dashboard to the customer's operations team.
AMOS engine that transforms observations into risk scores, probability estimates, and prioritised action lists.
The Risk Engine ingests observation data (condition scores, anomaly counts, change severity) and combines it with contextual factors (asset age, material type, environmental exposure, usage intensity) to produce risk assessments. It outputs: per-asset risk scores, portfolio-level risk distributions, time-to-intervention estimates, and cost-weighted priority rankings. The Risk Engine supports multiple risk models: structural failure, insurance claim likelihood, maintenance cost escalation, and safety incident probability.
In AAMOS
A property portfolio of 500 buildings is analysed. The Risk Engine identifies 23 buildings in the top risk decile, prioritises them by cost-of-failure × probability, and recommends: 5 immediate inspections, 12 planned repairs within 6 months, and 6 monitoring-only cases. Total estimated avoided cost: $2.3M.
S
See AMOS Safety.
API endpoint that assigns a numerical score to an image, object, or asset based on trained quality, risk, or condition models.
The /score endpoint produces calibrated numerical assessments. Unlike /classify (which assigns categories), /score returns a continuous value on a defined scale. Score types include: condition score (0–100, where 100 = perfect), risk score (0–100, where 100 = critical), quality score (0–100, where 100 = publication-ready), and custom scores trained for specific domains. Each score includes confidence intervals and the contributing feature breakdown.
API Usage
POST /score with {image: "base64...", score_type: "facade_condition"} returns {score: 67, confidence: 0.91, scale: "0-100", breakdown: [{feature: "crack_density", contribution: -12}, {feature: "cleanliness", contribution: +8}, ...]}.
API endpoint that performs instance segmentation — identifying the exact pixel boundaries of objects within an image.
The /segment endpoint goes beyond /detect (bounding boxes) to produce pixel-accurate masks for each detected object. Segmentation enables precise area measurement (e.g., "crack covers 0.34 m²"), damage quantification, and detailed visual analysis. It supports both semantic segmentation (class per pixel) and instance segmentation (individual object masks). Output includes polygon coordinates, mask area, and per-pixel confidence.
API Usage
POST /segment with {image: "base64...", model: "amos-infrastructure-v3.1", classes: ["crack", "spall", "stain"]} returns {segments: [{class: "crack", mask: "base64...", area_px: 2847, confidence: 0.93, polygon: [...]}, ...]}.
AI-guided capture mode that automatically detects when sufficient visual evidence has been collected and signals completion.
Smart Scan is the entry-level AVO mode. As the Zoomer captures images, AMOS Vision analyses them in real time and provides feedback: "Damage detected — capture closer," "Insufficient lighting — retry," "Object complete — move to next." When the sufficiency threshold is reached (trust_achieved ≥ trust_threshold), Smart Scan signals completion with a green indicator. This removes guesswork from field capture and ensures consistent evidence quality across different Zoomers and conditions.
In quiXzoom
A Zoomer photographs a damaged road surface. Smart Scan guides: "Crack detected. Step closer." They move closer. "Good. Capture 2 more angles." They do. "Evidence sufficient. Submit." The entire interaction takes 45 seconds and produces analysis-ready imagery.
The determination that enough evidence has been collected to support a verified claim — calculated per-claim, never globally.
Sufficiency is AVO's core decision function. For each verified_claim, the system accumulates evidence quality signals: image sharpness, coverage of required angles, presence of key features, liveness confirmation, and cross-validation consistency. The sufficiency formula is: trust_achieved = Σ (weight_i × confidence_i × liveness_factor). When trust_achieved ≥ trust_threshold, the claim is marked sufficient. The threshold is set per knowledge pack and per claim type — never globally. This ensures that a passport verification requires different evidence than a facade inspection.
In AAMOS
A vehicle wheel inspection requires: full tread visible, sidewall captured, valve stem readable, and reference object present. AVO accumulates trust for each element. After 4 photos, trust_achieved = 0.91, exceeding the 0.85 threshold. The claim is marked sufficient and the Zoomer is prompted to submit.
High-urgency mission deployment after acute events — storms, floods, accidents — offering elevated compensation for rapid documentation.
Surge events are time-critical mission activations triggered by disasters or emergencies. They carry 2–5× standard compensation to incentivise rapid response. Surge alerts are pushed as priority notifications to all Zoomers in the affected zone, with Professional tier Zoomers notified first. Surge missions typically have tighter specifications and stricter AI review given their legal and claims significance. They are the primary mechanism for post-disaster damage documentation.
In quiXzoom
A severe storm hits coastal Sweden. An insurer activates 40 surge missions across 12 postcodes within 20 minutes. Zoomers receive priority push notifications — missions pay $35 each (vs. $12 standard) with a 3-hour time window. 38 of 40 missions are claimed within 45 minutes.
V
A cryptographically signed, immutable assertion about physical reality — the unit of truth in the AAMOS evidence system.
A Verified Claim is not the image, not the evidence package, but the assertion itself: "Bridge 2847 has a crack 43cm long on the north facade, confidence 94%, observed 2026-07-12 09:47 UTC by Zoomer Z-2847." Each claim is signed with Ed25519, stored append-only, and includes provenance (who observed, what model analysed, what human reviewed). Corrections create new claims with backward references — the original remains immutable. Verified Claims are the currency of trust in the Landvex ecosystem.
In AAMOS
A bridge inspection produces 6 Verified Claims: "No structural damage (confidence 97%)", "Surface crack detected, 12cm (confidence 91%)", "Railing intact (confidence 99%)"... Each claim is signed, timestamped, and stored. An auditor can verify any claim's provenance back to the original observation.
API endpoint that checks whether an image, document, or asset meets specified criteria — the general-purpose validation interface.
The /verify endpoint is a flexible validation tool. It accepts criteria definitions ("must contain a face", "must show a readable serial number", "must be captured after 2026-01-01") and returns a pass/fail result with detailed reasoning. It is used for document verification, quality gate checks, compliance validation, and custom business rules. Criteria can be predefined (from knowledge packs) or custom (supplied in the API request).
API Usage
POST /verify with {image: "base64...", criteria: [{type: "contains", object: "face"}, {type: "readable", field: "serial_number"}, {type: "timestamp_after", date: "2026-01-01"}]} returns {passed: true, checks: [{criterion: "contains face", passed: true, confidence: 0.99}, ...]}.
Visual Infrastructure Monitoring System — Landvex product for continuous, AI-powered monitoring of critical infrastructure assets.
VIMS applies the AAMOS engine stack to critical infrastructure: bank ATMs, EV charging stations, traffic signals, utility meters, and safety equipment. It creates a visual baseline per object, then compares new observations against that baseline to detect tampering, damage, wear, or unauthorised modifications. Each anomaly is risk-classified (Green/Yellow/Orange/Red) and triggers appropriate alerts. VIMS combines quiXzoom field collection with AMOS analysis and Landvex decision delivery into a complete monitoring solution.
In Landvex
A bank deploys VIMS across 200 ATMs. Daily photos are compared against baselines. On day 47, VIMS flags one ATM with an Orange alert: the card reader area shows a new overlay not present in the baseline. A technician is dispatched within 2 hours. The overlay is a skimming device — caught before any customer data is compromised.
See AMOS Vision.