# Reaction Records - Duplicate Record Identity Checker

> Reaction Records - Duplicate Record Identity Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010316/call, status unknown (last checked 2026-10-16).

Compares duplicate owner, subject, and revision declarations in reaction records across every scientific frame to detect conflicting or redundant identities.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/reaction-records/duplicate-record-identities?utm_source=zero.xyz
- Price: $0.010316/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reaction-records-duplicate-record-identity-checker-bcd3fa4c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pTT-N_qncuCTClM5AVHnL

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 reaction-records-duplicate-record-identity-checker-bcd3fa4c -d '<json body>'
```

Example prompt: Can you check these reaction records for duplicate identity declarations — specifically look for conflicting owner, subject, or revision labels — the data is synthetic and has nonpersonal metadata only?

## When to prefer this

Use this endpoint when you need to detect duplicate or conflicting owner, subject, or revision identity declarations specifically within reaction records, and your data is either public or synthetic with nonpersonal metadata. Prefer this over general deduplication services when working within a scientific/chemistry record-keeping context where identity frame accuracy matters.

## Known failure modes

- Exceeds 32 row limit — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not explicitly set to true — request rejected
- Malformed rows array — schema validation failure
- Empty rows array — minimum items constraint violated

## How this service works

Compare duplicate owner/subject/revision declarations against every scientific frame Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured comparison of owner, subject, and revision identity declarations across submitted reaction record rows, flagging groups where duplicate or conflicting identities are found within the scientific frame. This is a supplied-record analysis, not an independent certification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reaction-records-duplicate-record-identity-checker-bcd3fa4c/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)