# Tempest AI Content Engine — Group Classification

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

Classifies text into user-defined categories using AI, as part of a broader 25-endpoint AI content engine

## Facts

- Endpoint: POST https://tempestars.vercel.app/api/group?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tempest-ai-content-engine-group-classification-5b3079b7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lQ3IY3yhR04bfTR_PCm7W

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-5b3079b7 -d '<json body>'
```

Example prompt: Classify this customer review using Tempest — is it a complaint, a compliment, or a feature request? The review says: 'The onboarding was smooth but I can't figure out how to export my data.'

## When to prefer this

Choose this endpoint when you need to classify text against a custom, user-defined set of categories rather than a fixed taxonomy. It is ideal for routing, labeling, and sorting workflows where the category list changes per use case. Prefer this over dedicated sentiment-only or topic-only classifiers when flexibility in category definitions is required. Best suited for pay-per-call usage patterns where you do not want to manage a hosted ML model.

## Known failure modes

- Missing required `text` field returns an error or empty result
- Ambiguous categories may cause misclassification or low-confidence output
- Very short or context-free text may yield unpredictable category assignments
- Exceeding token limits for long texts may cause truncation or failure
- Payment not included or insufficient USDC balance triggers x402 payment-required error

## 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 — typically the assigned category and any associated confidence or metadata returned by the AI model.

## 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-5b3079b7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tempestars.vercel.app](https://www.zero.xyz/host/tempestars.vercel.app/llms.txt)
