# Study Notes — Duplicate Record Identities

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

Groups study-note identities by notebook and revision, distinguishing matching from conflicting note digests to surface duplicate or inconsistent records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/study-notes/duplicate-record-identities?utm_source=zero.xyz
- Price: $0.010296/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/study-notes-duplicate-record-identities-583e318a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5LhZNTPnViKWyq3f4w5IP

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 study-notes-duplicate-record-identities-583e318a -d '<json body>'
```

Example prompt: Can you check these 15 study notes and tell me which ones share the same identity across notebooks and revisions — I want to know which are genuine duplicates with matching digests versus conflicting ones where the content differs? Data class is public and all metadata is non-personal.

## When to prefer this

Choose this endpoint when you need to reconcile a batch of up to 32 study-note records and determine whether identity collisions represent true duplicates (matching digests) or conflicting versions (same identity, different content), specifically within an offline, non-personal metadata context. Prefer it over general deduplication tools when the data is study-note structured records requiring notebook-and-revision-aware grouping.

## Known failure modes

- notes array empty or exceeds 32-item limit — validation error
- dataClass not one of 'public' or 'synthetic' — schema rejection
- nonpersonalMetadata not explicitly set to true — rejected as required const
- malformed note objects missing identity or digest fields — processing error
- service unavailable — HTTP 5xx after payment deducted

## How this service works

Group study-note identities by notebook and revision; distinguish matching from conflicting note digests. Different revisions are not collapsed into one identity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns study-note identities grouped by notebook and revision, with each group labelled as matching (identical digests) or conflicting (same identity but differing digests). Different revisions are kept distinct and not collapsed. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "notes": {
   "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/study-notes-duplicate-record-identities-583e318a/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)