# Provenance Manifests - Timestamp Order Audit

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

Audits declared timestamps in caller-supplied provenance manifests, checking issue/creation time, expiry, assessment time, expiry equality, and future-dated timestamps for logical ordering and consistency.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/provenance-manifests/timestamp-order-audit?utm_source=zero.xyz
- Price: $0.015307/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/provenance-manifests-timestamp-order-audit-9772f178
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bOnxKX7HfS-x_d5Uv-teI

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 provenance-manifests-timestamp-order-audit-9772f178 -d '<json body>'
```

Example prompt: Audit the timestamps in these 5 public provenance manifest rows — I need to check that the issue time, expiry, and assessedAt time are all in valid order, with no future-dated timestamps or expiry equality issues; nonpersonal metadata only.

## When to prefer this

Use this endpoint when you need an offline, structured audit of declared timestamps within caller-supplied provenance manifests — specifically to validate logical ordering of issue, expiry, and assessment times, detect future timestamps, and check expiry equality. It is not suitable for online freshness checks, downloading source artifacts, verifying cryptographic signatures, or checking scientific validity. Prefer this over general-purpose validation tools when your data class is strictly public or synthetic nonpersonal metadata and you need a receipted audit trail.

## Known failure modes

- Invalid or malformed timestamp strings cause parsing errors
- Rows array exceeds maxItems limit of 32, returning a 400 validation error
- Missing required nonpersonalMetadata field (must be true) causes rejection
- Invalid dataClass value outside enum [public, synthetic] causes 400 error
- Payment not supplied or insufficient USDC causes 402 response
- Rows array is empty (below minItems of 1) causes rejection

## How this service works

Check declared issue/creation time, expiry and assessment time, including expiry equality and future timestamps; not an online freshness check for caller-supplied artifact and dataset provenance manifests. No source download, build reproduction, signature verification, proof of origin, causality or scientific validity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns an audit result per manifest row indicating whether declared timestamps (issue/creation time, expiry, assessedAt) are in valid logical order, flags any future-dated timestamps, identifies expiry equality violations, and notes any assessment time anomalies. Full results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

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

## More

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