# TENNA Launch Intelligence – Batch Deployer & Launcher Check

> TENNA Launch Intelligence – Batch Deployer & Launcher Check 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).

Batch-checks deployer history and launcher classification for up to 20 Robinhood Chain token addresses, returning per-token rows with deployer and launcher metadata (no survival screen or safety verdict).

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/tenna/batch_screen
- 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-launch-intelligence-batch-deployer-launcher-check-8b5f2f0b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RAuH6YI1S4S1f0bBoAq-B

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-launch-intelligence-batch-deployer-launcher-check-8b5f2f0b -d '<json body>'
```

Example prompt: Can you batch-check the deployer history and launcher classification for these 20 Robinhood Chain token addresses using TENNA's batch_screen offering: 0xABC...001, 0xABC...002, ... 0xABC...020?

## When to prefer this

Choose this endpoint when you need to efficiently check deployer history and launcher classification for multiple Robinhood Chain tokens in a single call (up to 20). It is faster and more cost-effective than calling single-token endpoints repeatedly. Use it when you want raw deployer and launcher metadata without a full survival screen or safety verdict — for example, to filter a watchlist, cluster tokens by deployer, or enrich a dataset before further analysis.

## Known failure modes

- Token address not found in ledger — returns explicit row state with null component fields
- More than 20 token addresses submitted — request rejected (minItems:1, maxItems:20)
- Invalid token address format (not matching ^0x[a-fA-F0-9]{40}$) — validation error
- Chain value other than 'robinhood' specified — rejected by enum constraint
- Offering identifier not exactly 'batch_screen' — rejected
- Payment failure via x402 — endpoint not executed

## How this service works

Batch Deployer & Launcher Check. Batch deployer-history and launcher-classification check for up to 20 tokens. It does not run the survival screen or issue a token risk/safety verdict; it is never a safety verdict. Tokens absent from the ledger return an explicit row state and null component fields.

## Output

Returns a row per token address containing: deployer wallet launch history (number of prior launches, outcomes) and launcher classification (which launch system created the pool, on what basis, e.g. WET vs others). Tokens absent from the ledger return an explicit row state with null component fields. Does not include a survival screen or token risk/safety verdict.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "robinhood"
   ],
   "type": "string",
   "description": "Only 'robinhood' supported."
  },
  "offering": {
   "type": "string",
   "const": "batch_screen",
   "description": "Offering identifier. Must be exactly 'batch_screen'."
  },
  "tokenAddresses": {
   "type": "array",
   "items": {
    "type": "string",
    "pattern": "^0x[a-fA-F0-9]{40}$",
    "examples": [
     "0x0000000000000000000000000000000000000000"
    ]
   },
   "maxItems": 20,
   "minItems": 1,
   "description": "Token addresses (max 20)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tenna-launch-intelligence-batch-deployer-launcher-check-8b5f2f0b/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)