canonical: https://jentic.com/apis/safereel.ai/safereel

# SafeReel

The SafeReel API classifies images and videos as nsfw or clean so platforms can screen user uploads before they go live. Images get a synchronous verdict with a confidence score from POST `/v1/check`, and cached verdicts return instantly without being billed. Videos are scanned asynchronously from a public URL with no upload or file-size limit, returning a job to poll or a signed webhook callback, and the finished job reports how many frames were flagged and at which timestamps.

## For AI agents

Check an image for NSFW content and get a verdict with confidence, or queue a video scan by URL and read flagged frames and timestamps when the job is done.

## Scope

Does not detect violence, hate speech, or spam text, and does not host or transcode media. Use for nsfw or clean classification of images and videos only.

## Capabilities

- Classify one uploaded JPEG, PNG, or WebP image as nsfw or clean with a confidence score
- Queue a video scan from a public URL and receive a job id to poll
- Receive a signed webhook callback when a video scan finishes by setting webhook_url
- Read a video job's status, verdict, flagged frame count, and flagged_ts timestamps
- Make video submissions safe to retry with an Idempotency-Key header
- Check public service status and load before sending a large batch

## Use cases

### Upload moderation agent through Jentic

A community app wants an agent to screen new posts before they publish. Through Jentic the agent searches for 'check an image for NSFW content', receives the SafeReel operation with its input schema, and calls POST `/v1/check` with the uploaded image. It reads the verdict and confidence and holds any nsfw post for review, while clean posts go live.

Example prompt: Call POST `/v1/check` with the uploaded image file, then publish the post if verdict is 'clean' and hold it for review if verdict is 'nsfw' with confidence above 0.8

### Asynchronous video screening

Video platforms cannot block an upload request while a long clip is scanned. POST `/v1/videos` takes a public url and an optional webhook_url and returns a job id with status. GET `/v1/videos/{job_id}` reports queued, processing, done, or failed, and once done gives the verdict, the number of frames and flagged frames, and flagged_ts with the timestamps of flagged frames.

Example prompt: Call POST `/v1/videos` with url 'https://cdn.example.com/uploads/clip.mp4' and an Idempotency-Key header, then poll GET `/v1/videos/{job_id}` until status is 'done' and report flagged_ts

### Webhook-driven moderation pipeline

Instead of polling, a backend can pass webhook_url when submitting a video. The submit response includes a webhook_secret, returned only at submit time, that signs the webhook HMAC so the receiver can verify the callback came from SafeReel before acting on the verdict.

Example prompt: Call POST `/v1/videos` with url 'https://cdn.example.com/uploads/clip.mp4' and webhook_url 'https://example.com/hooks/safereel', and store the returned webhook_secret for HMAC verification

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/check` | Classify one image |
| POST | `/v1/videos` | Submit a video for scanning |
| GET | `/v1/videos/{job_id}` | Poll a video job |
| GET | `/v1/status` | Public service status |
| POST | `/v1/demo/check` | Anonymous demo image check |

## Key resources

- **Image checks** — Synchronous nsfw or clean verdict with confidence, model, and cached flag for one image, plus an anonymous demo check
- **Video jobs** — Video scan submission by URL with optional signed webhook, and job polling with flagged frames and timestamps
- **Service status** — Public status with load level and version, and a liveness probe

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 96 / 100
- **View full report:** https://jentic.com/apis/safereel.ai/safereel/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring SafeReel by hand means sending a bearer key, handling a synchronous image path and an asynchronous video path, polling jobs or verifying signed webhooks, and adding an Idempotency-Key for safe retries. Through Jentic you install once, import SafeReel from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** SafeReel puts the video job id in the URL path (`/v1/videos/{job_id}`), so a rule can let your agent read one job's result, while image checks are bounded by operation. You choose the operations it may call, so billable video submissions are not included unless you add them.
- **Credential handling:** Your SafeReel API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check an image for NSFW content' or 'scan a video for explicit content', and Jentic returns the matching SafeReel operation with its input schema so the agent calls the right endpoint without reading the docs.

## Related APIs

- **Image Moderation** — Image content rating for adult and teen content
- **Clarifai API** — General computer vision platform with moderation models
- **Mux API** — Video hosting, encoding, and streaming
- **Cloudinary Upload API** — Image and video upload and transformation

## FAQ

### What authentication does the SafeReel API use?

The SafeReel API declares an HTTP bearer scheme named HTTPBearer in its OpenAPI spec, used by POST `/v1/check`, POST `/v1/videos`, and GET `/v1/videos/{job_id}.` GET `/v1/status`, GET /health, and the POST `/v1/demo/check` demo need no auth. Through Jentic the bearer key is held by your own Jentic One instance and attached at call time.

### Can I scan long videos with the SafeReel API?

Yes. POST `/v1/videos` queues a scan from a public http or https URL with no upload and no file-size limit, and the spec notes every video bills at most 20 minutes. Poll GET `/v1/videos/{job_id}` or set webhook_url for a signed callback. Job ids are owner-only, so other keys get a 404.

### What are the rate limits for the SafeReel API?

The spec says POST `/v1/check` and the demo report rate-limit state in RateLimit-* response headers, and the anonymous demo is limited to 10 images per IP per day. It gives no fixed limit for keyed calls; check https://safereel.ai/docs for current plan limits.

### How do I check an image for NSFW content through Jentic?

Search Jentic for 'check an image for NSFW content', load POST `/v1/check`, and execute it with a JPEG, PNG, or WebP image of up to 10MB. The response gives verdict, confidence, model, and whether the result was cached. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a SafeReel MCP server?

You don't need an MCP server to give your agent SafeReel. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent finds the image check and video scan operations when it needs them.

### Can I limit what my agent is allowed to do with the SafeReel API?

Yes. For an image-only moderator, write a rule that allows only POST `/v1/check.` The agent can classify images but cannot queue billable video scans, and each call it makes is logged. Add POST `/v1/videos` and GET `/v1/videos/{job_id}` when you want it to handle video.
