Audits: check a photo you already have

A verification certifies a photo taken live, right now, through a link. An audit checks a file that already exists: a photo someone emailed you, one sitting in your system, one you downloaded. No link, no camera, no person on the other end. Rial runs three checks on every audited file, always: is it a photo of a screen, does it look AI-generated, and is it already online. Describe the photo (expectedObject, context) and it also checks that it shows that; send conditionAspects and it scores the condition. You don’t pick the checks. Because no device stood behind the photo, there is no rial: true/false; you get the checks that tripped and decide.

One call

import { readFile } from 'node:fs/promises';
import { createRial } from '@rial/sdk';

const rial = createRial({ apiKey: process.env.RIAL_API_KEY });

const result = await rial.audits.run({
  file: await readFile('claim-9912.jpg'),
  contentType: 'image/jpeg',
  expectedObject: '2021 Toyota Corolla',
  conditionAspects: ['paint', 'bumper'],
  metadata: { claimId: 'CLM-9912' },
});

audits.run uploads the file, starts the analysis and waits for the result. It takes a few seconds.

What you get back

{
  "id": "vfy_…",
  "status": "completed",
  "verdict": { "signals": [{ "type": "ai_detected", "confidence": 0.81 }] },
  "objectMatch": { "status": "match" },
  "condition": { "score": 7.5, "label": "good" }
}

verdict.signals lists the checks that tripped. Empty means all three ran and nothing tripped. screen_detected is a photo of a screen, ai_detected an AI-generated image, found_online an image already published. Every check runs; one tripping never stops the others, so two can appear together.
objectMatch says whether the photo shows your expectedObject.
condition scores each aspect 0 to 10 with a one-line reason.

Every field is explained in Verdicts.

Don’t wait

audits.create uploads and starts the analysis, then returns at once. Read the result later with verifications.get(id), or pass webhookUrl and Rial POSTs verification.completed to you.

const started = await rial.audits.create({
  file,
  contentType: 'image/jpeg',
  webhookUrl: 'https://your.app/rial',
  metadata: { claimId: 'CLM-9912' },
});
started.id; // vfy_…

Input

Field	Required	What it is
`file`	yes	The bytes: a `Buffer`, `Uint8Array` or `Blob`.
`contentType`	yes	`image/jpeg`, `image/png`, `image/webp`, `image/heic` or `image/heif`.
`expectedObject`	no	What must appear in the photo. Turns on the object check.
`conditionAspects`	no	Aspects to score, up to 6. Turns on the condition check.
`context`	no	`{ kind, summary }` describing what the photo is supposed to show. Turns on the context check.
`webhookUrl`	no	HTTPS URL that receives the result.
`metadata`	no	Your own keys, returned with the result and in webhooks.

Audits are billed like verifications. They go through the Node SDK today; for another language, write to developers@rial.io.

Start

Results

Audits

One call

What you get back

Don’t wait

Input

​One call

​What you get back

​Don’t wait

​Input

One call

What you get back

Don’t wait

Input