# Policy Excerpts Timestamp Order Audit

> Policy Excerpts Timestamp Order Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.015293/call, status unknown (last checked 2026-11-11).

Audits declared policy publication, effective, and withdrawal timestamps to detect inverted or out-of-order time windows across multiple policy versions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/policy-excerpts/timestamp-order-audit?utm_source=zero.xyz
- Price: $0.015293/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/policy-excerpts-timestamp-order-audit-210c47c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_21gTI7a2N_chYCFZrxlEy

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 policy-excerpts-timestamp-order-audit-210c47c0 -d '<json body>'
```

Example prompt: Can you audit these policy versions for timestamp ordering issues — specifically check whether any of them have publication dates that fall after their effective dates or withdrawal dates that are out of order? Use public data class and flag anything that looks like an inverted window.

## When to prefer this

Use this endpoint when you need to programmatically detect temporal ordering anomalies specifically in policy document lifecycles — particularly publication-after-effectiveness inversions — without performing legal validity judgments. Prefer this over general-purpose timestamp validators when your input is structured policy version metadata and you need audit-ready output with a defined retention policy. Best suited for compliance pipelines, governance tooling, or pre-publication QA workflows handling public or synthetic policy data.

## Known failure modes

- Missing or malformed timestamp fields in submitted policy versions may result in incomplete audit output
- Exceeding 32 versions per call returns a validation error
- Submitting personal metadata (nonpersonalMetadata must be true) will be rejected
- Invalid dataClass enum value (must be 'public' or 'synthetic') causes request failure
- Empty versions array (minItems:1 not met) returns a validation error

## How this service works

Check declared policy publication, effective and withdrawal times for inverted windows. Publication after effectiveness is reported, not judged invalid or unlawful. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A report identifying any policy versions where timestamps are out of expected order — specifically where publication dates fall after effective dates, or where withdrawal dates precede effective dates. Results include the flagged version identifiers and the nature of the inversion. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "versions": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/policy-excerpts-timestamp-order-audit-210c47c0/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)
