VISIONThe most cost-effective way to moderate live streams.
Let a model watch every stream at a low frame rate, check only the flags you act on, and send people only the moments it flags. With Detectivision, a session at 1 frame a second in detect mode costs 1 credit a minute, and you pay for the frames checked: what a session holds and does not use comes back.
Four things set the price
Frames a second
Most things worth moderating stay on screen for more than a second. Checking 1 frame a second costs a thirtieth of checking every frame of a 30 fps stream.
Mode
detect answers with flags only. capture adds where each finding is, and censor a blurred copy of each moment; both cost twice detect.
Flags
Name only the flags you act on. Models that feed none of them are not run, so frames are checked faster; fewer flags never cost more.
People for what is flagged
Moderators look at the flagged moments, each kept with its picture, instead of watching streams from start to end.
What a session costs
Credits per minute are the frames a second, rounded up, times the mode’s price.
| Session | Frames a second | Mode | Credits a minute | Credits an hour |
|---|---|---|---|---|
| Flags only | 1 | detect | 1 | 60 |
| With boxes | 1 | capture | 2 | 120 |
| Shorter moments | 2 | detect | 2 | 120 |
| Every frame of a 30 fps stream | 30 | capture | 60 | 3,600 |
Live sessions pay the price table and are never doubled. A minute is held ahead; when the session ends it keeps what its frames cost and the rest comes back.
Start a session
Give a stream link (RTSP, RTMP, HLS, HTTP or SRT) and our servers watch it, or send frames yourself from a browser camera or a device.
Flagged frames become moments
A flagged frame is kept with its picture, at most one every few seconds (3 by default), in your moderation history.
Get them as they happen
A live.moment webhook reaches your system for each moment, with the session’s metadata, so you can act at once.
Stop and settle
Stop the session when the stream ends, or it stops by itself. The credits its frames did not use come back.
A session at 1 credit a minute
curl https://api.detectivision.ai/api/v1/live/sessions \
-H "Api-Key: $DETECTIVISION_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"source": "url",
"url": "rtsp://cams.example.com/live",
"fps": 1,
"mode": "detect",
"flags": ["sexual", "violence"]
}'{
"id": 31,
"source": "url",
"fps": 1,
"mode": "detect",
"status": "running",
"framesChecked": 0,
"creditsCharged": 1,
"costPerMinute": 1
}The answer is shortened. costPerMinute is what a minute of this session costs; creditsCharged is the minute held ahead.
Frequently asked
What does live stream moderation cost with Detectivision?
At 1 frame a second, 1 credit a minute in detect mode and 2 in capture or censor mode. A higher rate costs that times the rate, rounded up: at 30 fps in capture mode, a minute is 60 credits.
How many frames a second should I check?
For most streams 1 or 2. A higher rate catches shorter moments and costs more. At high rates the models set the pace: with every flag on, about 25 frames a second are checked.
Is a whole minute charged when a session stops early?
No. A minute is held ahead; when the session ends it keeps what its frames cost and the rest goes back to your balance.
Which streams can be checked?
A stream link over RTSP, RTMP, HLS, HTTP or SRT on a public address, or frames you send yourself, for example from a browser camera.
Which plans include live stream credits?
The plans and the credits each gives, live stream credits among them, are on the pricing page.
Live stream moderation
Moderate streams and cameras as they air.
Pricing
The plans and what each check costs.
Video at scale
Recorded video: sample frames and check asynchronously.