AI Audit

The AI Audit node checks a Video Analysis result against the video it describes. It re-watches the clip, compares every claim in the analysis with the footage, and corrects only what the video itself confirms. Every outcome is disclosed in a report: what was fixed, what was proposed but declined, and what a person should look at.

On a self-hosted install, the node shows a NODARO mark and runs through your Nodaro Cloud connection, billed to the connected account. Without a connection, the node shows a Connect nodaro.ai button and does not run.

When to use it

• You want to check an analysis before you spend credits recreating every scene from it.
• You want to catch mistakes that one pass can miss. Examples are a misread camera move, a line of dialogue given to no one, or a slot description that drifts from the footage.
• You re-edited or re-uploaded a clip and want to re-check a saved analysis against it.

Quick start

Inputs

Outputs

Because the structure is the same, an audited analysis is a drop-in replacement. For example, the Auto-cast from analysis option of Generate Video Pro reads it with no change.

Settings

AI Audit has no settings: no quality tier and no options. The audit follows the footage. The only thing that changes its behavior and its price is whether an analysis is connected, and the settings panel says which case applies:

• Auditing the analysis from the connected node, with the credit range for a connected analysis.
• No analysis wired, with the higher credit range of the run that analyzes the video first.

The report

Every verdict of the re-watch lands in the report as one of three kinds. Nothing in the corrected analysis changes without a matching entry.

Each finding names the scene number, using the corrected analysis's own numbering, and gives a plain-language reason. Where it applies, a finding also names the field it concerns. The report starts with a one-line summary of the audit's verdict, and says whether the node had to analyze the video first.

A clean audit, with nothing corrected, refused or flagged, is a valid and common result: the analysis held up against the footage.

The report is shown on the node. It is not an output you can wire. Through the API and MCP, it is in the job's output_data.report, for example from get_job after a video_audit call.

Credits

The price depends on the length of the video and on whether an analysis is connected. The length falls into the smallest step that fits it: up to 60, 180, 360 or 600 seconds, the same steps as Video Analysis.

Example. A 72-second clip falls in the 180-second step. With a finished analysis connected, the audit is a re-check only and costs 291 credits. Without one, the node must first run its own fast analysis, so the same clip costs 477 credits.

Limits

• Maximum length: 10 minutes (600 seconds), the same as Video Analysis.
• No YouTube links. Connect a video node instead.
• The video is required. A run with nothing connected to Video is refused before any credits are reserved.
• A connected analysis must exist. If the Analysis input is connected to a node that has no result yet, the run is refused. It does not fall back to the more expensive run that analyzes the video first. Run the Video Analysis node first, or disconnect it.

Tips

• Connect the analysis whenever you have one. The audit is cheaper and checks the exact analysis you plan to use.
• Chain audits for a second opinion. One AI Audit's output can feed the Analysis input of another, for an independent second pass.
• Read the report even when nothing changed. A "nothing changed" summary with Watch findings still points at something worth checking.