# API Contracts — Timestamp Order Audit

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

Validates that HTTP API contract publication and retirement timestamps are in correct chronological order against a supplied assessment time.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/timestamp-order-audit?utm_source=zero.xyz
- Price: $0.015303/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-timestamp-order-audit-9c8be1e2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eOaoFm3HliR39shh6O_ld

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 api-contracts-timestamp-order-audit-9c8be1e2 -d '<json body>'
```

Example prompt: Can you audit the timestamp order on these 3 API contracts — they're public data — and check them against an assessment time of 2024-11-15T12:00:00Z to confirm publication comes before retirement and flag any open-ended contracts?

## When to prefer this

Use this endpoint when you need a lightweight, offline, typed audit of API contract timestamp sequencing — specifically to confirm publication precedes retirement and to surface open-ended (no retirement declared) contracts. Prefer it over general contract validators when you need deterministic chronological ordering checks on nonpersonal metadata without side effects or live freshness certification.

## Known failure modes

- Missing or malformed assessedAt timestamp causes validation failure
- Contracts array exceeds 32-item limit returns error
- dataClass value outside enum (public/synthetic) is rejected
- nonpersonalMetadata not set to true (const) causes schema rejection
- Contracts with incomplete timestamp fields may yield partial audit results

## How this service works

Check declared HTTP contract publication/retirement times against a supplied assessment. Missing retirement stays open-ended; no freshness, availability or execution certification. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a timestamp order audit report indicating whether each contract's publication and retirement times are in correct chronological sequence relative to the supplied assessment timestamp. Flags contracts with missing retirement dates as open-ended. No live availability or freshness data is certified. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "contracts": {
   "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/api-contracts-timestamp-order-audit-9c8be1e2/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)