# Recovery Manifests — Duplicate Record Identities

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

Groups recovery manifest IDs within payment, network, and revision frames to distinguish exact duplicates from conflicting result or deadline projections.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/duplicate-record-identities?utm_source=zero.xyz
- Price: $0.010302/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-duplicate-record-identities-a285878e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ldDYJ5UFXgMb0YOtDRUDa

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-duplicate-record-identities-a285878e -d '<json body>'
```

Example prompt: I have a batch of up to 32 public recovery manifest records and I need to group them by payment, network, and revision frames to find exact duplicates and flag any that have conflicting result or deadline projections — can you run the duplicate identity check on them?

## When to prefer this

Choose this endpoint when you need to identify and classify duplicate recovery manifest IDs across payment, network, and revision frames — especially when you need to distinguish true exact duplicates from records that conflict on result or deadline projections. It is ideal for offline, non-personal, typed metadata in public or synthetic data classes. Do not use this if you need replay, retry, or repayment functionality.

## Known failure modes

- Invalid or missing nonpersonalMetadata flag (must be true) causes rejection
- Manifest array exceeding 32 items returns a validation error
- Unsupported dataClass value (must be 'public' or 'synthetic') causes schema rejection
- Empty manifests array fails minItems constraint
- Malformed manifest objects may result in partial grouping or classification errors
- Results expire after 24 hours and are no longer retrievable

## How this service works

Group recovery manifest IDs within payment, network and revision frames; distinguish exact duplicates from conflicting result/deadline projections. No recovery replay, automatic retry or repayment. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns grouped recovery manifest IDs organized within payment, network, and revision frames, distinguishing exact duplicates from records with conflicting result or deadline projections. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No replay, retry, or repayment is performed.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/recovery-manifests-duplicate-record-identities-a285878e/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)