# LUMI Social Timing Check

> LUMI Social Timing 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).

Measures whether social media posts about a token led or lagged the price move, using timestamps recovered arithmetically from X (Twitter) Snowflake IDs.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/lumi/lumi_social_timing_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/lumi-social-timing-check-6a7bdbf7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_a_ZoFN3oWWrT0MFHUOGkS

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 lumi-social-timing-check-6a7bdbf7 -d '<json body>'
```

Example prompt: Can you run the LUMI social timing check on token address 0xabc123... to tell me whether the X posts about it came before or after the price moved?

## When to prefer this

Use this endpoint when you need to understand the historical relationship between social media activity and price movement for a specific token — particularly for due diligence, post-event auditing, or verifying claims about social media front-running. It is distinct from predictive or sentiment endpoints because it explicitly measures timing (lead vs lag) using Snowflake ID arithmetic rather than making forward-looking predictions.

## Known failure modes

- Invalid or missing token address returns an error
- Offering identifier not exactly 'lumi_social_timing_check' causes rejection
- Insufficient X post data for the token yields no timing result
- Payment of $0.01 USDC not processed via x402 protocol blocks the call
- Token address with no associated X post history cannot produce a result

## How this service works

Whether social posts led or lagged the price move, measured. Post times are recovered arithmetically from X snowflake ids. In our sample posts lagged the move, so this is a timing disclosure and never an early-warning or entry signal.

## Output

A timing disclosure report indicating whether X (Twitter) posts about the token were published before or after the price move occurred, with the post timestamps recovered arithmetically from Snowflake IDs. The result is explicitly a historical timing measurement, not a predictive or early-warning signal.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "offering": {
   "type": "string",
   "const": "social_timing_check",
   "description": "Offering identifier. Must be exactly 'social_timing_check'."
  },
  "tokenAddress": {
   "type": "string",
   "description": "Optional 0x token address to check."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lumi-social-timing-check-6a7bdbf7/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)