# Sky Observations Timestamp Order Audit

> Sky Observations Timestamp Order Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.015327/call, status unknown (last checked 2026-10-25).

Validates that sky-observation records are in correct collection/processing/export timestamp order and within a caller-defined maximum age, flagging ordering violations while tolerating absent and equal timestamps.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/sky-observations/timestamp-order-audit?utm_source=zero.xyz
- Price: $0.015327/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sky-observations-timestamp-order-audit-2b1587b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UDz8OlFAwgCP6eH212hR0

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 sky-observations-timestamp-order-audit-2b1587b4 -d '<json body>'
```

Example prompt: Can you audit these 20 sky observation rows to check that their collection, processing, and export timestamps are in the correct order and that none are older than 86400 seconds? The data class is 'public' and I'm assessing as of now.

## When to prefer this

Choose this endpoint when you need to verify the temporal ordering and age compliance of sky or celestial observation records before archiving, publishing, or downstream processing. It is specifically designed for astronomical/sky observation data with a flexible stance on absent timestamps (treated as unknown rather than invalid) and tolerates equal timestamps. Prefer it over generic timestamp validators when your domain is celestial observations and you need nuanced handling of missing processing/export timestamps.

## Known failure modes

- Fewer than 1 or more than 32 rows supplied — request rejected
- Invalid dataClass value outside 'public' or 'synthetic' enum — validation error
- maximumAgeSeconds outside 0–31536000 range — schema violation
- nonpersonalMetadata not set to true — required constant missing
- Malformed assessedAt timestamp string — parsing error
- Missing required fields in row objects — partial or full audit failure

## How this service works

Check collection/processing/export order and caller-defined maximum age; absent processing or export timestamps stay unknown, and equal timestamps are allowed for sky-observation export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit report indicating whether the sky-observation rows conform to the expected collection → processing → export timestamp ordering, identifies any violations or out-of-order entries, flags records exceeding the caller-defined maximum age, notes absent processing or export timestamps as unknown (not invalid), and confirms whether equal timestamps are acceptable. This is a supplied-record analysis, not an independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "assessedAt": {
   "type": "string"
  },
  "maximumAgeSeconds": {
   "type": "integer",
   "maximum": 31536000,
   "minimum": 0
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sky-observations-timestamp-order-audit-2b1587b4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)