# TENNA Batch Token Watchlist Screener

> TENNA Batch Token Watchlist Screener 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).

Screens up to 20 token addresses at once on the Robinhood chain, returning deployer history summaries and launcher risk classifications for each token.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/tenna/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-batch-token-watchlist-screener-52804389
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rnCzdZ7uMPaEq8brroTTK

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-batch-token-watchlist-screener-52804389 -d '<json body>'
```

Example prompt: Can you screen these 20 token addresses on the Robinhood chain for deployer risk using TENNA's batch screener — I want to know which ones have sketchy launcher histories before I add them to my portfolio: [list of addresses]?

## When to prefer this

Use this endpoint when you need to screen multiple tokens (2–20) simultaneously rather than making individual calls per token, saving cost and latency. Prefer this over the single-token TENNA endpoint whenever you have a watchlist or batch of addresses to evaluate. Best suited for pre-investment due diligence workflows, automated monitoring pipelines, or any scenario where a portfolio or list of tokens needs rapid risk triage on the Robinhood chain.

## Known failure modes

- Token address not found in TENNA ledger — returns null fields rather than a safe verdict
- More than 20 token addresses submitted — request rejected due to maxItems constraint
- Invalid token address format (not matching ^0x[a-fA-F0-9]{40}$) — validation error
- Chain other than 'robinhood' specified — enum validation failure
- Incorrect offering identifier — must be exactly 'tenna_batch_screen'
- Payment failure — x402 micropayment of $0.01 USDC not processed correctly

## How this service works

Watchlist screening for up to 20 tokens at once: deployer record summary and launcher classification per token. Same limits as the single-token offerings; tokens absent from the ledger return null fields, never a safe verdict.

## Output

For each submitted token address, the agent receives a deployer record summary (prior launch history, patterns) and a launcher classification (risk tier or label). Tokens not found in the TENNA ledger return null fields — absence of data is never interpreted as a safe 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-batch-token-watchlist-screener-52804389/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)