# Spectrometry Records - Duplicate Identity Checker

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

Compares duplicate owner, subject, and revision declarations across scientific spectrometry frame pins to detect identity conflicts in public or synthetic spectrum/calibration metadata.

## Facts

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

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 spectrometry-records-duplicate-identity-checker-3721fd8d -d '<json body>'
```

Example prompt: Can you check these spectrometry records for duplicate owner and subject declarations across the frame pins? I have up to 20 public spectrum metadata rows and want to know which ones have conflicting or repeated identity fields.

## When to prefer this

Choose this endpoint when you need to validate spectrometry or calibration metadata records specifically for duplicate owner, subject, or revision identity declarations across frame pins, using only public or synthetic (non-personal, non-raw-instrument) data. It is not suitable for raw instrument file parsing, peak identification, compound inference, or any medical/laboratory use. Prefer it over generic deduplication tools when your records are structured scientific spectrum metadata that maps to the spectrometry frame-pin identity model.

## Known failure modes

- Input exceeds 32 KiB limit — request rejected
- dataClass not set to 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true — request rejected
- Fewer than 1 or more than 32 rows submitted — schema validation failure
- Malformed row data that cannot be parsed against frame pin structure — partial or full error response
- Service unavailable — HTTP 5xx with no result

## How this service works

Compare duplicate owner/subject/revision declarations against every scientific frame pin. Bounded public or synthetic spectrum/calibration metadata only; no raw instrument file parsing, hardware calls, peak identification, compound inference, medical interpretation, calibration-performance guarantee or laboratory instructions. Supplied source pins are not verified source bytes. Input limit: 32 KiB. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

The endpoint returns a structured report identifying which rows among the submitted spectrometry records have duplicate or conflicting owner, subject, or revision declarations relative to the scientific frame pins, including which records triggered matches and the nature of the identity conflict. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## 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/spectrometry-records-duplicate-identity-checker-3721fd8d/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)