# TENNA Sell Execution Check

> TENNA Sell Execution 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).

Checks whether actual sell transactions have executed in a token pool on-chain, returning observed sell count and total swap count from TENNA's chain node.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/tenna/tenna_sell_execution_check
- 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-sell-execution-check-d7c9f51d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cbc6AmgPFKJxA2KxuHs0t

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-sell-execution-check-d7c9f51d -d '<json body>'
```

Example prompt: Check if sells have actually executed for the token at 0xABC123...def456 on the Robinhood chain — I want to see the observed sell count and total swaps from TENNA's chain node.

## When to prefer this

Choose this endpoint when you need a quick, low-cost on-chain observation of whether real sell transactions have executed in a token pool — particularly useful for pre-trade due diligence on new token launches or when evaluating honeypot risk. Prefer this over static contract audits when you need live execution evidence rather than code analysis. Note: this is limited to the Robinhood chain pilot and does not provide honeypot certification or smart contract security guarantees.

## Known failure modes

- Invalid or malformed token address (not matching 0x + 40 hex chars) returns a validation error
- Unsupported chain value (only 'robinhood' is accepted in pilot) returns an error
- Token address with no on-chain activity may return zero counts rather than an error
- Network or node unavailability may result in timeout or incomplete data
- Incorrect offering identifier (must be exactly 'tenna_sell_execution_check') causes request rejection

## How this service works

Did sells actually execute in this pool? Returns observed sell count and total swaps from our chain node. An execution observation, not a contract audit and not a honeypot certification.

## Output

Returns an execution observation object containing the number of observed sell transactions and total swap count recorded by TENNA's chain node for the specified token pool. This is an on-chain observation only — not a smart contract audit and not a honeypot certification.

## 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": "sell_execution_check",
   "description": "Offering identifier. Must be exactly 'sell_execution_check'."
  },
  "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-sell-execution-check-d7c9f51d/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)