# TENNA Launch Intelligence – Deployer Launch History

> TENNA Launch Intelligence – Deployer Launch History 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 single deployer wallet address, including total launches, outcome distribution by loss band, profitable rate, and median terminal multiple.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/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-launch-intelligence-deployer-launch-history-4286ddee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DS-7K3OHW6Iw0_lv4HhUA

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-deployer-launch-history-4286ddee -d '<json body>'
```

Example prompt: Can you pull up the full launch history for deployer wallet 0xAbCd1234... on TENNA — I want to see how many launches they've done, what percent were profitable, and their median terminal multiple?

## When to prefer this

Use this endpoint when you need a historical track record for a specific deployer wallet address — particularly before evaluating a new token launch from that deployer. Prefer this over the batch endpoint when you only need a single address. Prefer this over the token-level evidence report when you want deployer-level aggregate stats rather than per-launch details. This endpoint is read-only and returns factual historical data, not predictions.

## Known failure modes

- Invalid or malformed EVM address (must be 0x-prefixed 40-hex-char address) returns a validation error
- Unknown deployer address with no recorded launch history returns empty or zero-count record
- Incorrect offering identifier (must be exactly 'deployer_record') returns an error
- Payment failure via x402 protocol results in no data returned
- Network timeout or upstream data unavailability may return a service error

## How this service works

Deployer Launch History. 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 historical record for the specified deployer wallet including: total number of observed launches, how those launches ended broken down by loss band categories, the overall profitable rate as a percentage, and the median terminal multiple across all launches. This is a factual historical record with no forward-looking predictions or trading signals.

## 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-launch-intelligence-deployer-launch-history-4286ddee/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)