# Robotics Telemetry - Duplicate Record Identity Checker

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

Detects and groups duplicate owner, subject, and revision declarations within robotics telemetry records by comparing them against scientific frame boundaries.

## Facts

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

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 robotics-telemetry-duplicate-record-identity-checker-e00c7140 -d '<json body>'
```

Example prompt: Can you check these robotics telemetry rows for duplicate owner, subject, and revision declarations — they're public data with no personal metadata — and tell me which records are duplicates within the same scientific frame?

## When to prefer this

Choose this endpoint when you need to detect duplicate owner, subject, or revision declarations specifically within robotics telemetry data framed by scientific context. It is suited for pre-ingestion data quality checks on batches of up to 32 public or synthetic (non-personal) telemetry records. Prefer it over generic deduplication tools when your data is structured as scientific telemetry frames and you need frame-aware duplicate grouping rather than simple field-level deduplication.

## Known failure modes

- Submitting more than 32 rows returns a validation error
- Missing or false nonpersonalMetadata flag causes rejection
- Invalid dataClass value (not 'public' or 'synthetic') causes schema error
- Empty rows array fails minItems validation
- Malformed row objects may result in incomplete comparison results

## 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 analysis of which submitted telemetry rows share duplicate owner, subject, or revision declarations within the same scientific frame boundaries, grouping the matching records and identifying the specific conflicting fields. This is a supplied-record analysis only and does not constitute 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/robotics-telemetry-duplicate-record-identity-checker-e00c7140/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)