Your product returns the equipment, the likely fault, and the parts to bring — without a technician looking at it first. The SpotFix API does the diagnosis; your brand does the talking.
Three response tiers · Seconds to identify, minutes for a full report
Most integrations don't need a full diagnostic on every case. Start with identification, add reasoning when the conversation warrants it, and pull the complete report only when someone is about to act on it.
Make, model, serial, age, refrigerant and voltage, read from the customer's photo of the nameplate. For a lot of partners this alone answers the question — it's enough for an agent to quote the right part on the first call.
POST /cases/:id/identify
A ranked, preliminary set of likely causes, reasoning over the evidence already collected rather than re-analysing the media. Call it after each answer and it narrows as the conversation goes. Returned marked preliminary, and it means it.
POST /cases/:id/shortlist
Ranked causes with what to verify first, parts to bring with ratings where they were read rather than inferred, estimated duration, and safety flags. Delivered by webhook when analysis completes.
GET /cases/:id/report
Identification and full reports are billed separately, so you only pay for the depth each case actually needs.
Customers photograph the wrong thing. Rather than failing on thin evidence, the intake asks for what's missing — based on what it can actually see — and tells you when it has enough to be useful.
One call returns a session token. No customer account, no app install.
Photos and video, as many as the customer sends.
Each turn returns the next question worth asking, grounded in the evidence so far.
Close intake and start analysis. The report arrives on your webhook.
The same case can return different views depending on who's reading it. Set a default per key, or override per request.
Ranked causes, what to verify first, safety flags, estimated duration. The technician's view.
Components with ratings and quantities, flagged where a rating was read from a label versus inferred. The parts counter's view.
Scope and summary written for matching a job to the right pro, without the internal diagnostic detail.
Assessment framed for a claim, including what the evidence does not establish.
Your logo, your colours, your domain. Customers and vendors never see ours unless you want them to.
Switch on per key. Strips customer address and contact details — useful when a report goes to several vendors before one is chosen.
Reports delivered when analysis completes, signed with a per-key secret so you can verify they came from us.
Monthly quota and per-minute rate limit set per key, with usage reporting you can pull at any time.
The fastest way to know whether this fits is to describe one real case from your platform — what the customer sends you today, and what you wish you knew before dispatching anyone.