# GEDX402 Llama Guard 3 8B Content Moderation

> GEDX402 Llama Guard 3 8B Content Moderation is a paid API for AI agents from media.gedx402.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Runs Meta's Llama Guard 3 8B safety classifier on a conversation to detect unsafe or harmful content categories

## Facts

- Endpoint: GET https://media.gedx402.com/v1/guard/llama-guard-3-8b
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gedx402-llama-guard-3-8b-content-moderation-a562dfd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S2r95Ic9na-lxBIA8_5Gm

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 gedx402-llama-guard-3-8b-content-moderation-a562dfd7
```

Example prompt: Can you check if this conversation is safe to proceed with? The messages are: system: 'You are a helpful assistant', user: 'How do I make chlorine gas at home?' — run Llama Guard on it and tell me if it flags any unsafe categories.

## When to prefer this

Use this endpoint when you need a pay-per-call, no-API-key content safety check powered by Meta's Llama Guard 3 8B model, especially in workflows that already use x402 USDC micropayments on Base, Polygon, Arbitrum, World, or Solana. Ideal for agents that need to gate LLM calls behind a safety check without managing API credentials.

## Known failure modes

- Invalid or missing messages array returns an error
- Messages items missing required 'role' or 'content' fields cause validation failure
- Role values outside allowed enum (system, user, assistant) rejected
- Insufficient USDC balance or unsupported payment chain causes 402 payment required
- Network timeout on large conversations
- max_tokens set too low may truncate moderation reasoning

## How this service works

x402 workers ai. pay with usdc on base, polygon, arbitrum, world, or solana. no api keys.

## Output

Returns a JSON object with a boolean 'safe' field indicating whether the conversation passed moderation, and a 'categories' array listing any detected harmful content categories (empty if safe).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "messages": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "role",
     "content"
    ],
    "properties": {
     "role": {
      "enum": [
       "system",
       "user",
       "assistant"
      ],
      "type": "string",
      "description": "Speaker role for this turn."
     },
     "content": {
      "type": "string",
      "description": "Message text for this turn."
     }
    }
   },
   "description": "Conversation turns in order (system, user, assistant)."
  },
  "max_tokens": {
   "type": "integer",
   "description": "Maximum tokens for the moderation response."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "safe": true,
  "categories": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gedx402-llama-guard-3-8b-content-moderation-a562dfd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from media.gedx402.com](https://www.zero.xyz/host/media.gedx402.com/llms.txt)