Documentation

Using AuroraView.

Most people never need this page — open the portal, drop photos in and export the result. This is for getting the most out of each workflow, and for wiring one into software you already run.

The workflows

There is nothing to choose in the portal — it is one drop zone and one question, and the question is already written for you. That runs Look at these, the first workflow below. The tuned ones after it are for callers using the API, where you name one explicitly; to get that shape out of the portal instead, say so in the question: "Write this up as an inspection report."

Each workflow reads every photo on its own terms, then writes one document across all of them. That second pass is why twenty photos come back as a single report instead of twenty disconnected notes.

Look at these

Up to 20 photos, and the one the portal runs. Per photo it names the subject, then splits what it sees in two: findings, the things that genuinely deserve a second look, and routine, what is simply present and unremarkable. Every finding carries where it is in the frame, how prominent it is, and one plain sentence on why it is worth your attention. The report opens with the single most important thing across the whole set, merges anything seen in more than one photo, and keeps the ordinary contents to a line at the end.

An empty findings list is a real answer, not a failure — if nothing stands out, it says so rather than inventing significance. Whatever you type in the question steers what it treats as worth noticing, so "focus on anything water-related" narrows it and "write this up as a condition report" changes the shape of the write-up.

Virtual Insurance Adjuster

Up to 20 photos. Per photo it records the view, the dominant construction material, permanent features and each visible defect with a severity of none, minor, moderate or severe and a location. The report consolidates duplicates — the same defect photographed twice is one finding — and ends with what the photos do not cover, which is the line that keeps a file honest.

It does not estimate costs and it will not report damage it cannot see. If you need a repair estimate, that is a judgement call for you, not for the photos.

Satellite Aerial Triage

Up to 12 aerial or GIS screenshots. Per parcel: canopy and cleared percentages, terrain, visible road access, structures and water features, plus a confidence level. The summary gives a one-line verdict per parcel and splits them into worth-a-look and pass, naming the disqualifying feature. Feed it screenshots in the order of your list and the verdicts come back in that order.

MLS Listing Builder

Up to 30 photos. Per photo: room, visible selling features, materials and finishes, condition, and one sentence of accessible alt text. The report is a headline, two or three paragraphs, and up to six highlight bullets.

It will not state square footage, lot size, age, school district or price — none of that is visible in a photograph, and a listing description that invents them is a problem you do not want. It also describes the property rather than the buyer, which keeps the copy on the right side of fair housing rules. Read it before you publish it.

Ask Anything

Up to 8 images and your own instruction. Ask for one thing and say what shape you want it in — "Reply with only a number." or "Reply as JSON with keys make, model, colour." — and that is what comes back, per image.

Writing good context

The three fixed workflows already know their job, so the context box is for what the photos cannot tell them: an address, a claim number, "focus on the north slope", "the garage is not part of this claim". Short and specific beats long. Anything you put there appears in the report's framing, so do not paste anything you would not want in the finished document.

Exporting

Limits

12 MB an image or a PDF, of which the first 8 pages are read. A conversation runs to 30 messages. 1,000 characters of context on a write-up. Jobs run one at a time, so a busy moment queues you rather than failing — the portal tells you where you are in line. A twenty-photo inspection takes roughly a minute.

The free trial is 10 images a day per visitor, with every workflow and every export unlocked. Paid plans lift that to a monthly allowance; enter the key we send you from the button in the top right of the portal and it is remembered in that browser.

Your photos and documents

In a write-up, each image is deleted the moment it has been read — before the report is even finished. A conversation is the one thing that has to keep your upload longer, because a second question about a document you no longer hold is not a thing we can answer: it stays in memory for the length of your chat, never touches a disk, and is dropped when you start a new chat, when you close the tab, or after thirty idle minutes.

Either way nothing is retained afterwards, nothing is used for training, and everything runs on hardware we own and operate in the United States. Nothing you upload is passed to a third-party service.

Calling it from your own software

On Studio and Scale plans the same workflows are available over HTTP: one image, one JSON response. Authenticate with the key we issued.

curl https://auroraview.tech/v1/analyze \
  -H "Authorization: Bearer $NTC_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "workflow": "adjuster", "image": "<base64 jpeg>" }'

{
  "model":    "auroraview-1",
  "workflow": "adjuster",
  "result": {
    "view":       "roof, north slope",
    "material":   "architectural asphalt shingle",
    "features":   ["chimney", "ridge vent"],
    "damage": [{
      "item":     "hail bruising",
      "severity": "moderate",
      "location": "upper third of the slope"
    }],
    "confidence": "high"
  }
}

Pass "workflow": "custom" with your own "prompt" for a free-text answer instead of fields. GET /v1/usage with the same header reports where the key stands this month.

Open the portal →