# LUMI X Post Timestamp Verification

> LUMI X Post Timestamp Verification is a paid API for AI agents from app.tenna.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Derives the exact publication timestamp of X (Twitter) posts arithmetically from their snowflake IDs, without external API calls or model inference.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/lumi/post_timestamp_verify?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lumi-x-post-timestamp-verification-dd3eaa12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Je_ApaPV8-6R8WAw8kH39

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-x-post-timestamp-verification-dd3eaa12 -d '<json body>'
```

Example prompt: Can you verify the exact timestamps for these X posts and confirm whether they were published before March 1st 2024? Here are the URLs: https://x.com/user1/status/1234567890123456789 and https://x.com/user2/status/9876543210987654321 — use the post_timestamp_verify offering.

## When to prefer this

Choose this endpoint when you need deterministic, auditable proof of when an X post was published — especially for legal, journalistic, or compliance use cases where model guessing is unacceptable. Prefer this over scraping Twitter's API (which requires auth and may rate-limit) or asking an LLM to infer dates (which can hallucinate). Ideal when verifying whether cited social media evidence predates a specific event, and when you need batch verification of up to 50 posts in a single call.

## Known failure modes

- Unparseable or malformed X post URLs return null rather than an error or estimate
- Non-x.com URLs will fail to parse and return null
- Batch exceeds 50 URLs — request rejected
- Incorrect offering identifier causes rejection
- URLs without a valid snowflake status ID return null

## How this service works

X Post Timestamp Verification. Verify when X posts were actually published. Timestamps are derived arithmetically from the snowflake id in each URL — no external API call, no model guessing. Unparseable URLs return null rather than an estimate. Useful for auditing whether cited evidence existed at a claimed time.

## Output

For each submitted X post URL, the endpoint returns the arithmetically derived publication timestamp extracted from the snowflake ID embedded in the URL. Returns null for any URL that cannot be parsed rather than guessing. No external API is called — the result is deterministic and based purely on the snowflake ID arithmetic.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "urls": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 50,
   "minItems": 1,
   "description": "x.com/<handle>/status/<id> URLs."
  },
  "offering": {
   "type": "string",
   "const": "post_timestamp_verify",
   "description": "Offering identifier. Must be exactly 'post_timestamp_verify'."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lumi-x-post-timestamp-verification-dd3eaa12/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)