# Publication Records Timestamp Order Audit

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

Audits the declared chronological order of issue, update, and retrieval timestamps in a publication record against a specified assessment instant.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/timestamp-order-audit?utm_source=zero.xyz
- Price: $0.015332/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-timestamp-order-audit-48a07f3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_za9eVqNb-jjVN0SfaTDdd

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 publication-records-timestamp-order-audit-48a07f3e -d '<json body>'
```

Example prompt: Check whether the declared issue, update, and retrieval timestamps in this publication record are in the correct chronological order — the DOI is 10.1234/example.2023.001, publisher is SpringerNature, and assess it as of 2024-06-15T00:00:00Z, treating it as public data.

## When to prefer this

Use this endpoint when you need to verify the internal chronological consistency of timestamps declared in a single publication, DOI, edition, or snapshot record against a known assessment instant. Prefer this over general metadata validators when the specific concern is temporal ordering of issue/update/retrieval dates within a bibliographic or scholarly publishing context.

## Known failure modes

- Invalid or malformed DOI returns validation error
- assessedAt timestamp in unrecognized format causes parsing failure
- rows array empty or exceeds 32 items triggers schema rejection
- nonpersonalMetadata not set to true results in request rejection
- Missing required fields (doi or assessedAt) returns 400-level error
- dataClass enum value outside 'public' or 'synthetic' causes rejection

## How this service works

Check declared issue/update/retrieval chronology against an assessment instant in one exact publisher/work/DOI/edition/snapshot Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an analysis of the declared timestamp sequence (issue, update, retrieval dates) in the supplied publication record, indicating whether the chronological order is consistent with the specified assessment instant. Results reflect supplied-record analysis only, not independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "doi": {
   "type": "string",
   "maxLength": 200,
   "minLength": 8
  },
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "workRef": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "assessedAt": {
   "type": "string"
  },
  "editionRef": {
   "type": "string"
  },
  "publisherRef": {
   "type": "string"
  },
  "metadataDigest": {
   "type": "string"
  },
  "metadataRevision": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/publication-records-timestamp-order-audit-48a07f3e/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)