Mechanical condition intelligence for Mojaz.
Extend existing vehicle inspections with acoustic analysis, OBD context and the PTX mechanical-health signal—then deliver findings into the Mojaz experience your inspectors and customers already know.
A new data layer. Not another inspection platform.
Mojaz already performs vehicle inspections and produces reports. AutoSonix is designed to complement—not replace—those workflows by turning mechanical sounds and selected onboard diagnostics into structured assessment data.
Listen beyond fault codes
Sound can reveal an audible mechanical anomaly even when no diagnostic trouble code has been stored.
Standardize the result
Present acoustic findings, OBD context and PTX output in a repeatable format for review and triage.
Keep Mojaz in front
In a production integration, assessment data can be incorporated into Mojaz's own report rather than requiring customers to open a second application.
Four components. One connected assessment.
AutoSonix has evolved from its original auction-focused application into a broader assessment infrastructure. The underlying flow remains straightforward.
Data collection
ListenLink records engine sound. A Bluetooth OBD adapter captures available vehicle signals. A guided iOS or Android app ties the inspection to the vehicle.
Auto-AI
Purpose-built acoustic models evaluate recorded sound patterns, supported by the available vehicle and operating context.
PTX + findings
The Powertrain Index combines relevant assessment inputs into a decision-ready score and supporting finding categories.
Portal + partner API
Reports can be reviewed in AutoSonix's portal or made available as structured results through a partner API.
The 38-second figure was stated for the audio segment; total time depends on setup, data capture, operator and vehicle conditions. Pilot performance and vehicle coverage remain to be validated in the intended fleet.
Designed to fit a physical vehicle inspection.
For initial validation, Mojaz inspectors can use the AutoSonix application without requiring changes to Mojaz's production software.
Available acoustic + vehicle context
- Engine mechanical sound and anomaly categories
- Available OBD DTCs, warning status and readiness monitors
- Operating conditions, including available coolant temperature and RPM
- Vehicle identification, mileage and capture context
Screening is not workshop diagnosis
- AutoSonix does not replace an Autel or Launch workshop scan tool
- Stationary recording cannot identify every fault that only appears while driving
- A non-running engine cannot be acoustically assessed in the normal recording procedure
- OBD data breadth varies across vehicles, especially where nonstandard protocols are involved
Two stages: validate first, integrate second.
In our October 29, 2026 discussion, Mojaz described a preference for using its own Flutter application and delivering assessment information directly in its existing reports. The staged approach below supports that destination without delaying a technical pilot.
Separate capture, joint evaluation
Use AutoSonix's current application, sensor package and portal while measuring real-world compatibility and assessment usefulness.
- Mojaz inspectors use the iOS or Android capture app
- AutoSonix receives and analyzes data
- Named Mojaz evaluators access completed results
- Teams compare results with inspection findings
- No change required to Mojaz's production app
Embedded Mojaz experience
After a successful evaluation, scope an SDK-based capture experience in Mojaz's Flutter application, plus a data feed for Mojaz-owned report presentation.
- SDK adaptation and app embedding to be designed
- AutoSonix supplies inference and structured results
- Server-side partner API for completed reports
- Map records to Mojaz IDs and VINs
- Mojaz chooses which approved findings to display
Vehicle identity
Acoustic + available OBD capture
Acoustic analysis + context
PTX + structured findings
Vehicle record matching
Mechanical-condition display
Structured findings, not just an audio file.
The technical value lies in delivering a usable mechanical assessment, supporting diagnostic context and a way to review the underlying sound when appropriate.
Closer Look
Example classification, not a live Mojaz assessment- ✓PTX score and explanatory bandA compact mechanical-health signal for screening or triage, with context rather than a number alone.
- ✓Sound determinationsOverall acoustic classification and available engine/transmission findings, including a readable summary.
- ✓OBD and emissions contextReported trouble codes, code descriptions, MIL state and applicable readiness results.
- ✓Evidence linkSupporting engine sound may be available for review alongside the completed assessment.
- ✓Vehicle and report identifiersVIN, completion time and assessment ID; Mojaz's own record identifier can be echoed when supplied in integrated capture.
Connect the report to what was actually observed.
The technical review included a live portal walkthrough and discussion of sample vehicle findings. Approved real-world recordings and case reports can be shared as supporting material after appropriate access and confidentiality checks.
Recorded engine sound
Listen to the captured sound alongside the model's acoustic determination, when a suitably authorized and privacy-cleared example is provided.
Evidence provided separatelyCompleted vehicle report
Review a finished assessment showing the original findings, PTX category, diagnostic context and the associated recording.
Evidence provided separatelyInspector capture demonstration
View how an inspector connects hardware, records an engine and uploads the assessment, including relevant setup and safety steps.
Evidence provided separatelyThese are evidence categories to accompany the technical reference, not links to media currently embedded on this page. The assessment panel above is an illustrative example, not a substitute for an actual completed report.
Validate on Saudi-market vehicles—not assumptions.
Vehicle compatibility was identified as the principal gating issue, particularly the mix of Japanese, Korean, Chinese and other vehicles encountered locally. The pilot should answer that with actual field data.
| Question | How to test it | What to record |
|---|---|---|
| Does capture work? | Test representative local makes, model years and operating conditions. | Successful session rate; incomplete scans; time spent; reason for failures. |
| What OBD data is available? | Compare VIN, DTCs, readiness and live context against available workshop tools. | Supported fields by vehicle; missing/limited fields; incompatible cases. |
| Does sound analysis help? | Include vehicles with known conditions and independent inspection findings. | Agreement, misses, false alerts and useful condition observations. |
| Can inspectors use it consistently? | Have several Mojaz operators complete the guided capture in the field. | Training burden, repeatability, device-handling and workflow friction. |
| Can results fit Mojaz? | Agree on a sample Mojaz report layout and desired data fields. | Matching rules, display choices, media links and privacy constraints. |
A focused Mojaz evaluation.
Start small, get representative results, then decide together whether a deeper product integration is justified.
Gasoline-powered passenger vehicles and pickup trucks only in the pilot.
NDA + scope
Complete mutual confidentiality terms, identify evaluation owners and confirm test location, vehicle mix and pilot goals.
Equip the team
Provision two to three inspectors, coordinate sensor kits and app access, and provide a short onboarding session.
Assess vehicles
Complete a jointly agreed sample of vehicles, compare findings against actual inspection evidence and document compatibility.
Review outcomes
Agree whether results justify technical scoping, field mapping, Flutter SDK work and an eventual commercial structure.
From Mojaz
- Primary technical and business contacts
- Names and email addresses of pilot inspectors
- Representative vehicle types and inspection location
- Existing inspection report sample, if shareable
- Preliminary evaluation volume and success criteria
From AutoSonix
- Mutual NDA and pilot outline
- Sensor and OBD packages; shipping arrangement
- Account provisioning and operator training
- Access to completed assessment results
- Approved technical examples and follow-up discussion
Answers to the issues raised.
These clarifications are based on the October 29, 2026 technical conversation.
Does AutoSonix replace Autel or Launch scanners?
No. AutoSonix focuses on acoustic mechanical-condition screening, supported by standard OBD readings where available. It is not a full workshop diagnostic device and does not perform the manufacturer-level control or programming functions of professional scan tools.
Will it work with Japanese and Chinese vehicles?
The pilot is limited to gasoline-powered passenger vehicles and pickup trucks. Its sound-analysis approach is designed to work across many gasoline makes and models, but compatibility with Mojaz's actual Saudi-market fleet has not been independently validated. OBD field availability can vary. That is a primary purpose of the proposed pilot.
How long does the inspection take?
The guided audio segment is approximately 38 seconds in the workflow demonstrated. OBD connection, VIN confirmation, sensor placement, optional photo and upload make the entire assessment longer; actual total time should be recorded during the pilot.
Can it detect all transmission problems without driving?
No. The stationary workflow can observe available OBD faults and certain sounds associated with stationary gear engagement, where the process is safe. It cannot assess shift behavior or sounds that only occur while the vehicle is moving.
What if a vehicle has no stored fault codes?
A vehicle may still exhibit an audible abnormal mechanical sound. AutoSonix analyzes sound separately and considers available OBD context, readiness monitors and other information when producing its assessment. The absence of codes does not guarantee mechanical health.
What if a car has been sitting for months or will not start?
The workflow can consider some observed operating context, including available temperature information. The standard engine-sound assessment requires an operating engine; a non-running vehicle should be treated as a limitation or separate evaluation case.
Do Mojaz customers need to install another app?
Not in the intended production model. For the initial pilot, named inspectors can use the AutoSonix collection app. Later, a separately scoped Flutter SDK integration could embed collection in Mojaz's existing inspector workflow, and Mojaz could receive completed results through the partner API.
Can Mojaz display the assessment inside its own reports?
That is the proposed integration objective. The existing partner API is designed to deliver structured results, and the final UI/data fields would be selected and tested jointly. A linked report or embedded data presentation are possible design paths, not completed Mojaz features.
Where is the data processed and how is it protected?
Hosting, security and data-handling details will be reviewed with Mojaz after a mutual NDA is signed. Saudi data-residency, retention and permission requirements must be reviewed before committing to production.
Is PTX a confirmed vehicle diagnosis?
No. PTX is a screening and triage aid derived from available assessment signals. A qualified inspection or further diagnosis may be required to confirm a defect, and local accuracy/coverage should be established through the pilot.
Define the evaluation. Get the right vehicles. Review the findings.
AutoSonix and Mojaz can use a narrowly scoped pilot to determine whether the platform adds reliable and operationally useful mechanical-condition information to Mojaz's existing services.
Tom Allen · AutoSonix
tom.allen@autosonix.ai
autosonix.ai