# Scientific Dataset Records - Identifier Crosswalk Audit

> Scientific Dataset Records - Identifier Crosswalk Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035298/call, status unknown (last checked 2026-10-20).

Checks one-to-one alias mappings against typed identifier pins in scientific dataset records, auditing crosswalk consistency without certifying ownership or authenticity.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/scientific-dataset-records/identifier-crosswalk-audit?utm_source=zero.xyz
- Price: $0.035298/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scientific-dataset-records-identifier-crosswalk-audit-4ec48a19
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hX9ZuWBN6M7LD1OMWTEih

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 scientific-dataset-records-identifier-crosswalk-audit-4ec48a19 -d '<json body>'
```

Example prompt: Can you audit the identifier crosswalk for these 10 public scientific dataset records? I have rows of dataset entries and their alias mappings — I need to know if each alias correctly matches its typed pin, with nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need to audit one-to-one identifier alias crosswalks in scientific dataset records against typed pins, specifically for public or synthetic (non-personal) data. It is appropriate when you need systematic crosswalk consistency checking rather than ownership verification or full certification. Prefer this over general data validation tools when working with scientific dataset identifiers and alias mapping tables.

## Known failure modes

- More than 32 rows or mappings supplied — request rejected due to maxItems constraint
- nonpersonalMetadata not set to true — validation fails
- dataClass not set to 'public' or 'synthetic' — enum validation error
- Mismatched row and mapping counts leading to incomplete audit coverage
- Malformed identifier formats in rows or mappings causing parse errors

## How this service works

Check one-to-one aliases against every typed pin; identifier mapping does not establish ownership, rights or authenticity for repository/dataset/schema/method/revision-pinned manifest Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit of each alias-to-pin mapping in the supplied rows and mappings, reporting which one-to-one aliases match or conflict with their typed identifier pins, without asserting ownership, rights, or authenticity over the records.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "mappings": {
   "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/scientific-dataset-records-identifier-crosswalk-audit-4ec48a19/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)