# TENNA Launcher Classification

> TENNA Launcher Classification is a paid API for AI agents from app.tenna.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Identifies which launch system created a given token pool on Robinhood chain, distinguishing WETH-paired meme launchpads from VIRTUAL-paired launchers without claiming official Virtuals affiliation unless independently verified.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/tenna/tenna_launcher_classification
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tenna-launcher-classification-c483a6b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_egI4WaV_w0xKX49RO59Dk

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 tenna-launcher-classification-c483a6b8 -d '<json body>'
```

Example prompt: Can you classify the launcher for token 0xAbCd1234...5678 on the robinhood chain — I need to know whether it came from a WETH-paired meme launchpad or a VIRTUAL-paired launcher?

## When to prefer this

Use this endpoint when you need to determine the provenance of a token launch specifically on the Robinhood chain — particularly when distinguishing between WETH-paired meme launchpads and VIRTUAL-paired launchers matters for trading decisions, research, or due diligence. Prefer this over generic blockchain explorers when you need opinionated, verified launcher classification with explicit disclaimers about Virtuals affiliation.

## Known failure modes

- Invalid or malformed token address returns validation error
- Unsupported chain (anything other than 'robinhood') returns error
- Token address not found in known launch pool data returns unknown or null classification
- Incorrect offering identifier returns rejection
- Network or provider downtime causes timeout

## How this service works

Which launch system created this pool, and on what basis. Distinguishes WETH-paired meme launchpads from VIRTUAL-paired launchers. Never claims a launcher is an official Virtuals system without independent verification.

## Output

Returns the launch system that created the token's pool, including the launcher name or type, the pairing basis (WETH vs VIRTUAL), and a note on whether the launcher has been independently verified as an official Virtuals system.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "robinhood"
   ],
   "type": "string",
   "description": "Only 'robinhood' is supported in this pilot."
  },
  "offering": {
   "type": "string",
   "const": "launcher_classification",
   "description": "Offering identifier. Must be exactly 'launcher_classification'."
  },
  "tokenAddress": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{40}$",
   "examples": [
    "0x0000000000000000000000000000000000000000"
   ],
   "description": "20-byte EVM token address."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tenna-launcher-classification-c483a6b8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from app.tenna.ai](https://www.zero.xyz/host/app.tenna.ai/llms.txt)