# TENNA Deployer Launch Record

> TENNA Deployer Launch Record 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).

Returns the full observed launch history for a specific EVM deployer wallet, including launch count, outcomes by loss band, profitable rate, and median terminal multiple.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/tenna/tenna_deployer_record
- 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-deployer-launch-record-dd7ddd43
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9jGFiv-uImCeB1-47y9s5

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-deployer-launch-record-dd7ddd43 -d '<json body>'
```

Example prompt: Can you pull the TENNA deployer record for wallet 0x1234567890abcdef1234567890abcdef12345678 and tell me how many launches they've done, what their profitable rate is, and what their median terminal multiple looks like?

## When to prefer this

Use this endpoint when you need on-chain historical performance data for a specific EVM deployer wallet, particularly to assess their past token launch track record before engaging with a new project they've deployed. Prefer this over generic blockchain explorers when you need pre-computed metrics like profitable rate, loss band distribution, and median terminal multiple in a single call.

## Known failure modes

- Invalid or malformed EVM address returns a validation error
- Deployer address with no observed launches returns empty or zero-count record
- Incorrect 'offering' identifier (not exactly 'tenna_deployer_record') causes request rejection
- Payment failure or insufficient USDC balance results in 402 error
- Network or upstream data unavailability causes timeout or 5xx error

## How this service works

Full observed launch history for one deployer wallet: how many launches, how they ended by loss band, profitable rate, and median terminal multiple. Historical record, not a prediction. No trading signals or safety guarantees.

## Output

A structured historical record for the queried deployer wallet containing: total number of launches observed, distribution of launch outcomes categorized by loss bands, the percentage of launches that were profitable, and the median terminal multiple across all launches. Explicitly not a prediction or trading signal.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "offering": {
   "type": "string",
   "const": "deployer_record",
   "description": "Offering identifier. Must be exactly 'deployer_record'."
  },
  "deployerAddress": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{40}$",
   "examples": [
    "0x0000000000000000000000000000000000000000"
   ],
   "description": "20-byte EVM address that created the pool."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tenna-deployer-launch-record-dd7ddd43/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)