# LUMI X Post Timestamp Verifier

> LUMI X Post Timestamp Verifier 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).

Derives the true publication timestamp of X (Twitter) posts from their snowflake IDs, enabling verification that cited posts actually existed at a claimed time.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/lumi/lumi_post_timestamp_verify
- 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-x-post-timestamp-verifier-bccd2f22
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GA2yLjlRMU938RNSspzdK

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-verifier-bccd2f22 -d '<json body>'
```

Example prompt: Can you verify when these X posts were actually published — https://x.com/elonmusk/status/1234567890123456789 and https://x.com/nasa/status/9876543210987654321 — I need to confirm they existed before March 1, 2024.

## When to prefer this

Choose this endpoint when you need a deterministic, API-free, tamper-evident way to establish the publication timestamp of X posts — especially for evidentiary, legal, or journalistic use cases where model guessing is unacceptable. Prefer it over scraping or Twitter API lookups when you need zero-dependency, offline-computable verification that can be audited. It is particularly valuable when verifying that cited social media evidence predated a specific real-world event.

## Known failure modes

- Unparseable or malformed X post URLs return null rather than an error or estimate
- URLs missing a valid snowflake status ID cannot be decoded
- Non-X (Twitter) URLs will fail to parse and return null
- Batch limit of 50 URLs exceeded returns a validation error
- Missing or incorrect 'offering' field value causes request rejection

## How this service works

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, returns the derived publication timestamp extracted arithmetically from the snowflake ID embedded in the URL. Returns null for any URL that cannot be parsed (e.g. malformed, missing snowflake ID). No external API calls or model estimation are involved — the result is deterministic and exact.

## 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-verifier-bccd2f22/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)