# Reaction Records Timestamp Order Audit

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

Validates the chronological ordering of collection, processing, and export timestamps in declared reaction records, and checks whether records fall within a caller-defined maximum age window.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/reaction-records/timestamp-order-audit?utm_source=zero.xyz
- Price: $0.015316/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reaction-records-timestamp-order-audit-be3c220c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xwyLiQMZsXpiBvM7iV4Zb

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 reaction-records-timestamp-order-audit-be3c220c -d '<json body>'
```

Example prompt: Audit these 5 reaction record rows for correct timestamp ordering — collection before processing before export — and flag any records older than 86400 seconds; treat them as public synthetic data assessed as of now.

## When to prefer this

Use this endpoint when you need to programmatically audit the chronological integrity of reaction record timestamps (collection, processing, export) and enforce a maximum record age, especially in data pipelines or quality gates where you supply your own record declarations and need per-row ordering verdicts without independent certification.

## Known failure modes

- rows array empty or exceeds 32-item limit — request rejected
- maximumAgeSeconds outside 0–31536000 range — validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — invalid enum error
- assessedAt missing or malformed — age check may be skipped or error returned
- malformed row objects — individual row results may be unknown or error flagged

## 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 declared reaction record Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit report for each submitted reaction record row indicating whether the timestamp sequence (collection → processing → export) is valid, which timestamps are absent or unknown, whether equal timestamps are permitted, and whether any records exceed the caller-specified maximum age threshold. Does not independently certify the data — analysis is based solely on the supplied record declarations.

## 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/reaction-records-timestamp-order-audit-be3c220c/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)