# Recovery Manifests — Unit-label consistency

> Recovery Manifests — Unit-label consistency is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.012302/call, status unknown (last checked 2026-10-15).

Validates that TTL unit labels (seconds, milliseconds, hours) in payload and receipt fields of recovery manifests match the declared retention contract, without converting units or accessing storage.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012302/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/recovery-manifests-unit-label-consistency-654cede3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fCaa659gj_tuoQOTl58er

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 recovery-manifests-unit-label-consistency-654cede3 -d '<json body>'
```

Example prompt: Check these 5 recovery manifests for TTL unit-label consistency — I expect all time-to-live fields to be in seconds, the data is synthetic and nonpersonal, and I need to know if any payload or receipt labels say milliseconds or hours instead.

## When to prefer this

Use this endpoint when you need to verify that TTL unit labels in recovery manifests literally match a declared retention contract unit without any unit conversion, store access, or deadline renewal. It is ideal for offline metadata auditing of nonpersonal, public or synthetic manifest data where you specifically want a label-level consistency check rather than a semantic value equivalence check. Prefer it over general schema validators when the concern is specifically mismatched time-unit label declarations between payload and receipt fields.

## Known failure modes

- Manifests array exceeds 32 items — request rejected with validation error
- Missing or invalid expectedUnit enum value — request fails schema validation
- nonpersonalMetadata not set to true — request rejected as it only accepts nonpersonal data
- Malformed manifest objects with missing TTL fields — may result in incomplete or error-flagged output
- Invalid dataClass value outside 'public' or 'synthetic' enum — request fails validation

## How this service works

Compare payload and receipt TTL unit labels against the declared retention contract. Seconds, milliseconds and hours are not converted; no store access or deadline renewal. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A consistency report indicating whether the payload and receipt TTL unit labels across all submitted manifests match the declared expected unit (seconds, milliseconds, or hours), with per-manifest details on any mismatches or label deviations found. No unit conversion is performed and no store access occurs.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/recovery-manifests-unit-label-consistency-654cede3/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)