# Tempest AI Content Engine — Group Classification

> Tempest AI Content Engine — Group Classification is a paid API for AI agents from trempest.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-16).

Classifies text into one or more user-defined categories using AI, returning a structured group/classification result

## Facts

- Endpoint: POST https://trempest.vercel.app/api/group
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tempest-ai-content-engine-group-classification-789aee77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OYfrjTD4tJ3T09X6ozT9i

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 tempest-ai-content-engine-group-classification-789aee77 -d '<json body>'
```

Example prompt: Classify this customer support message — 'My order hasn't arrived and no one is responding to my emails' — into one of these categories: [billing, shipping, account, general] using Tempest's group classification endpoint.

## When to prefer this

Use this endpoint when you need to route, sort, or label free-form text into predefined buckets at scale, especially when you want to define your own task framing and category list. Prefer Tempest's /api/group over generic LLM calls when you need a pay-per-call classification service with a structured response schema and no infrastructure overhead.

## Known failure modes

- Missing required 'text' field returns a 400-level error
- Empty or null category list may cause unstructured or undefined output
- Ambiguous task description may yield low-confidence or incorrect classification
- Payment not sent or insufficient USDC results in 402 Payment Required
- Very long text inputs may exceed model context limits
- Category list with overlapping definitions may produce inconsistent results

## How this service works

Compose, rewrite, translate, and refine content at scale. 25 AI-powered endpoints. Pay-per-call with USDC on Tempo.

## Output

Returns a JSON object with a 'success' boolean and a 'data' object containing the classification result, indicating which category or group the input text belongs to based on the defined task and provided categories.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "text"
 ],
 "properties": {
  "task": {
   "type": "string",
   "description": "Classification task"
  },
  "text": {
   "type": "string",
   "description": "Text to classify"
  },
  "categories": {
   "type": "array",
   "description": "Categories"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object"
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tempest-ai-content-engine-group-classification-789aee77/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from trempest.vercel.app](https://www.zero.xyz/host/trempest.vercel.app/llms.txt)