# Recovery Manifests Timestamp Order Audit

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

Validates expiry declarations on result/receipt recovery manifests against original creation timestamps and retention windows, detecting invalid deadline extensions without performing any writes or payment recovery.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/timestamp-order-audit?utm_source=zero.xyz
- Price: $0.015302/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/recovery-manifests-timestamp-order-audit-63f87743
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TtJI-MB3ZeWHMv6oDLdkl

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 recovery-manifests-timestamp-order-audit-63f87743 -d '<json body>'
```

Example prompt: Audit these 5 recovery manifests for me — they're all public, synthetic data, with a content retention window of 86400 seconds and a receipt retention window of 7776000 seconds. Check if any of the expiry declarations are invalid or if someone tried to extend a deadline beyond what's allowed.

## When to prefer this

Use this endpoint when you need a purely offline, read-only audit of recovery manifest expiry declarations — especially when you want to detect attempted deadline extensions or confirm timestamp ordering without triggering journal writes, payment recovery, or any state changes. Prefer this over live recovery endpoints when compliance checking or pre-submission validation is the goal, and when all data is public or synthetic (non-personal).

## Known failure modes

- Manifests array is empty or exceeds 32 items — request rejected with validation error
- nonpersonalMetadata is not set to true — required const field causes rejection
- contentRetentionSeconds or receiptRetentionSeconds outside 0–31536000 range — rejected
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- Malformed manifest entries that cannot be parsed for timestamp fields — partial or full failure
- Missing required fields in individual manifests — entries flagged as unauditable

## How this service works

Check supplied result/receipt expiry declarations against original creation and retention windows, including attempted deadline extension. No journal writes or payment recovery is performed. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a validation report indicating which submitted manifests have expiry declarations that pass or fail against the stated content and receipt retention windows, flagging any detected deadline extension attempts or timestamp ordering violations. No data is written, no payments are recovered — the response is purely an offline audit result.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/recovery-manifests-timestamp-order-audit-63f87743/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)