# Orbital Records Identifier Crosswalk Audit

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

Audits one-to-one alias mappings for orbital record identifiers against typed pins, checking consistency without establishing ownership or authenticity.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/orbital-records/identifier-crosswalk-audit?utm_source=zero.xyz
- Price: $0.035238/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orbital-records-identifier-crosswalk-audit-e3dffb19
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t5UcaB9G7ihVAlN6aI2a9

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 orbital-records-identifier-crosswalk-audit-e3dffb19 -d '<json body>'
```

Example prompt: Can you audit these orbital record identifier alias mappings for me — I have up to 20 rows and 20 mappings using public-class data, and I want to check that each alias correctly matches its typed pin without any crosswalk inconsistencies?

## When to prefer this

Choose this endpoint when you need to audit identifier alias consistency in orbital record datasets without requiring full certification of ownership or authenticity. Best suited for pre-publication checks, data pipeline validation, or quality assurance workflows involving celestial/orbital identifier crosswalks with up to 32 rows and mappings.

## Known failure modes

- More than 32 rows or mappings submitted — request rejected with validation error
- dataClass value not in allowed enum ('public' or 'synthetic') — schema validation failure
- nonpersonalMetadata not set to true — request rejected
- Empty rows or mappings arrays — minimum item constraint violation
- Malformed identifier or mapping objects — parsing error returned

## How this service works

Check one-to-one aliases against every typed pin; identifier mapping does not establish ownership, rights or authenticity for target/centre/frame/time-scale/solution-pinned orbital Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit report indicating whether each declared identifier alias correctly maps one-to-one against its corresponding typed pin in the orbital records, flagging any inconsistencies, mismatches, or unresolvable aliases. Does not certify ownership, rights, or authenticity.

## 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/orbital-records-identifier-crosswalk-audit-e3dffb19/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)