# LUMI Social Post Timing Check

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

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

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/lumi/social_timing_check
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lumi-social-post-timing-check-11ad88c6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Lah9XwcPfdnadhOUFbtrf

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-post-timing-check-11ad88c6 -d '<json body>'
```

Example prompt: Can you run the LUMI social timing check on token 0x1234...abcd to tell me whether the social posts on X came before or after the price moved — I want to know if social was leading or lagging the action?

## When to prefer this

Use this endpoint when you need to understand the chronological relationship between social media activity and price moves for a specific token — especially to verify whether social posts were predictive (leading) or reactive (lagging). Prefer this over general sentiment endpoints when you need arithmetically grounded timestamp recovery from X Snowflake IDs rather than content-based sentiment scoring. Note: this endpoint explicitly documents that posts lagged in its sample, making it a transparency/disclosure tool rather than a signal generator.

## Known failure modes

- Invalid or missing token address returns an error or empty result
- Offering identifier not set to exactly 'social_timing_check' causes rejection
- Token with no social post history returns no timing data
- Snowflake ID recovery may fail for deleted or private posts
- Payment of 0.01 USDC not settled via x402 results in 402 Payment Required
- Token address not found on supported chains returns no data

## How this service works

Social Post / Price Timing Check. Whether social posts led or lagged the price move, measured on Robinhood-chain token launches only — not BTC, ETH or listed majors. Post times are recovered arithmetically from X snowflake ids. The sample is small, outcome-selected from pumped launches, and can be weeks old; its age in days ships with the result. In our sample posts lagged the move, so this is a timing disclosure and never an early-warning or entry signal.

## Output

Returns a timing disclosure showing whether social media posts about the token preceded or followed the price move, with the measurement derived arithmetically from X Snowflake IDs. Explicitly flags that in the sample, posts lagged the price move, so this is a disclosure of timing order and not an early-warning or trade entry 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-post-timing-check-11ad88c6/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)