# Grant Records - Timestamp Order Audit

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

Validates the chronological ordering of publication and amendment timestamps within a grant record against a single assessment instant and a half-open availability window.

## Facts

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

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 grant-records-timestamp-order-audit-16d81c7e -d '<json body>'
```

Example prompt: Audit the timestamp ordering on this grant record — the agency is HHS, opportunity ref OP-2024-001, program ref PRG-4422, jurisdiction US-Federal, assessed at 2024-06-15T12:00:00Z, data class public, with notice digest abc123 and revision 2; I need to confirm the publication and amendment instants are in the right order.

## When to prefer this

Choose this endpoint when you need to verify the chronological integrity of grant record timestamps — specifically publication and amendment instants — against a defined assessment point and availability window. Best suited for compliance pipelines that must confirm temporal ordering before ingesting or publishing grant data, not for independent certification or live grant database lookups.

## Known failure modes

- Missing or malformed assessedAt timestamp causes validation failure
- Rows array exceeds maxItems limit of 32
- Invalid dataClass enum value (must be 'public' or 'synthetic')
- Ambiguous or unparseable instant strings result in error
- nonpersonalMetadata not set to true const value causes rejection
- Missing required agencyRef or opportunityRef fields

## How this service works

Compare supplied publication/amendment instants and an explicit half-open availability window against one assessment instant, in an identical issuer/record/source/revision Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit report indicating whether the publication and amendment instants are in valid chronological order relative to the supplied assessment instant, and whether the record falls within the declared half-open availability window. Includes per-row results for batch inputs and identifies any ordering violations or window mismatches.

## Request schema (JSON Schema)

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

## More

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