fixRAgent triages a maintenance photo: what it is, how urgent, who to call, what to say right now.

The Triage Profile — one photo, one real call

No photo is shown on this sheet: the photo behind this Triage Profile is a user upload, held under a licence that covers processing only, so the Triage Profile's structure is shown with the engine's own words and coordinates.

What the engine looked at

1. 01Furnace[676, 237, 1000, 824]
2. 02Air Handler[336, 264, 680, 796]
3. 03Ductwork[0, 0, 350, 999]

Each box is the engine's own [ymin, xmin, ymax, xmax] for this photo on a 0–1000 scale; nothing is listed that it did not return.

The shape — the same fields, every call

is_building_assetasset_typeasset_categoryphoto_subjectreport_photo_agreementfault_detectedfault_visible_in_photofault_summaryfault_classesseveritytiercriterion_1_firedtier_forced_byvisible_wiringwater_near_electricalsafety_hazardhazard_detailtrade_requiredconfidenceresident_explanation

Every reply carries all of these under core, in this order; the payload on the right shows a subset of them with this call's values.

The payload — one fixed JSON shape, every call

{
  "diagnosis_id": "2a0a447e-9ef1-4ec2-bde0-46ef5e7088bb",
  "engine_version": "engine-v2-vote-1.0.0",
  "config_id": "engine-v2.deep.gemini-3-5-flash-lite.a1_rubric_v11.n5",
  "agreement": { "mode": "deep", "n": 5, "k": 5, "decided": true },
  "core": {
    "is_building_asset": true,
    "asset_type": "Gas Furnace and Air Handler",
    "asset_category": "HVAC",
    "fault_detected": false,
    "fault_classes": [],
    "severity": "P4",
    "tier": "WHENEVER",
    "criterion_1_fired": false,
    "tier_forced_by": null,
    "trade_required": null
  },
  "callback_url": "/api/outcome?diagnosis_id=2a0a447e-9ef1-4ec2-bde0-46ef5e7088bb"
}

Abridged: 10 of the 20 core fields, values verbatim from the call on the left. The full shape, field by field, is at fixragent.com/docs. The urgency word is assigned by the server from a fixed decision table, never taken from the model. Your developers map this to your work-order fields.

The API door

curl -X POST "https://fixragent.com/api/triage?config=deep" \
  -H "Content-Type: application/json" -H "x-triage-key: $TRIAGE_DEMO_KEY" \
  -d "{\"image\":\"$(base64 -w0 photo.jpg)\",\"mimeType\":\"image/jpeg\"}"

Same engine, headless. A diagnosis_id and a callback_url come back with every triage; tell us what it turned out to be and that answer joins the record. Keys are issued by hand today — ask at fixragent.com/docs.

The pilot offer

Send us last month's 25 closed work orders. We triage them blind. You compare.

You already hold the answer key: what each one turned out to be, who went, and when. We send back a tier, a trade and a say-this line per photo, without seeing your closeouts. The comparison table is yours either way.

To take it up: email legal@fixragent.com with how many work orders and which month. A person answers; nothing is automated on our side.