# Alloy Measurements - Duplicate Record Identity Comparison

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

Detects and groups duplicate owner/subject/revision declarations in alloy measurement records across scientific frames without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/duplicate-record-identities?utm_source=zero.xyz
- Price: $0.01032/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-duplicate-record-identity-comparison-aabb65e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_muuTHVD4a5iVhGKQ370FV

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 alloy-measurements-duplicate-record-identity-comparison-aabb65e5 -d '<json body>'
```

Example prompt: Check these alloy measurement rows for duplicate owner, subject, and revision declarations — the data is classified as synthetic and contains no personal metadata — and tell me which records share identical identities across scientific frames.

## When to prefer this

Choose this endpoint when you need to detect duplicate identity declarations (owner, subject, revision) within alloy measurement records across scientific frames, especially when working with public or synthetic datasets that carry no personal information. It is a record-analysis tool, not an independent certification service, so prefer it for data quality control and pre-ingestion deduplication rather than authoritative scientific validation.

## Known failure modes

- Empty or missing rows array returns validation error
- rows array exceeding 32 items rejected
- dataClass value outside 'public' or 'synthetic' enum rejected
- nonpersonalMetadata not set to true (const constraint) causes rejection
- Malformed row objects may produce incomplete duplicate groupings
- Network timeout for large row payloads

## 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 grouped sets of duplicate alloy measurement records that share identical owner, subject, and/or revision declarations within scientific frames, enabling callers to identify and resolve redundant entries in their supplied dataset.

## 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/alloy-measurements-duplicate-record-identity-comparison-aabb65e5/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)
