# slinkylayer.ai Explicit Content Detector

> slinkylayer.ai Explicit Content Detector is a paid API for AI agents from x402.slinkylayer.ai, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-15).

Analyzes an image URL for explicit or sensitive content using a selectable AI provider (Azure, Google, etc.) and returns a detection result.

## Facts

- Endpoint: POST https://x402.slinkylayer.ai/api/v1/proxy/a0755425-9710-49f2-aca7-463d72f7db2a/explicit-detect
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-slinkylayer-ai-6af756f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__j2Hk5hP_A2bYteng-6n-

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-slinkylayer-ai-6af756f3 -d '<json body>'
```

Example prompt: Can you check this image for explicit or sensitive content using Azure — here's the URL: https://example.com/uploads/photo123.jpg — and tell me if it's safe to publish?

## When to prefer this

Use this endpoint when you need to screen images for explicit or NSFW content before publishing, storing, or displaying them, especially when you want flexibility to choose between AI providers like Azure or Google. Prefer this over building your own moderation pipeline when cost-per-call economics ($0.20 USDC) and provider flexibility matter.

## Known failure modes

- Invalid or inaccessible image URL returns an error
- Unsupported requested_service value causes provider resolution failure
- Missing required fields (url or requested_service) returns validation error
- Provider API key invalid or missing when required causes authentication failure
- Image format not supported by the selected provider
- Network timeout if image URL is slow to fetch

## How this service works

Analyze an image file for explicit or sensitive content using the selected AI provider. Supports Azure, Google, and others as requested_service.

## Output

Returns a structured result indicating whether the image contains explicit or sensitive content, based on the selected AI provider's analysis (Azure, Google, etc.), potentially including category labels and confidence scores.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url",
  "requested_service"
 ],
 "properties": {
  "url": {
   "type": "string"
  },
  "requested_service": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "input": {
  "type": "http",
  "method": "POST",
  "bodyType": "json",
  "bodyFields": {
   "url": {
    "type": "string",
    "required": true
   },
   "azure_key": {
    "type": "string",
    "required": false
   },
   "google_key": {
    "type": "string",
    "required": false
   },
   "azure_endpoint": {
    "type": "string",
    "required": false
   },
   "requested_service": {
    "type": "string",
    "required": true
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-slinkylayer-ai-6af756f3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.slinkylayer.ai](https://www.zero.xyz/host/x402.slinkylayer.ai/llms.txt)