# Api Contracts — Identifier Crosswalk Audit

> Api Contracts — Identifier Crosswalk Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035088/call, status unknown (last checked 2026-10-23).

Validates one-to-one client aliases against exact HTTP contract owner, revision, input, and output pins to verify mapping integrity without proving discovery integration or tool availability.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/identifier-crosswalk-audit?utm_source=zero.xyz
- Price: $0.035088/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-identifier-crosswalk-audit-1e72d5e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_56SOnP0drXc1MBEWHpqrH

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 api-contracts-identifier-crosswalk-audit-1e72d5e5 -d '<json body>'
```

Example prompt: Audit my identifier crosswalk — I have 3 client aliases and 3 contracts I want to check; the data is public and nonpersonal metadata only. Can you verify that the aliases map one-to-one to the correct contract owner, revision, and input/output pins?

## When to prefer this

Choose this endpoint when you need a lightweight, offline, typed audit of identifier-to-contract crosswalk integrity — specifically to verify that client aliases resolve one-to-one to exact HTTP contract owner, revision, input, and output pins. It is not suited for live discovery integration checks, authority verification, or confirming tool availability; it operates strictly on nonpersonal metadata.

## Known failure modes

- Alias array exceeds 32 items — returns validation error
- Contract array exceeds 32 items — returns validation error
- dataClass not set to 'public' or 'synthetic' — returns enum validation error
- nonpersonalMetadata not set to true (const constraint) — returns rejection
- Mismatched array lengths between aliases and contracts may yield incomplete audit results
- Empty alias or contract arrays rejected due to minItems:1 constraint

## How this service works

Check one-to-one client aliases to exact HTTP contract owner/revision/input/output pins. Aliases do not prove discovery integration, authority or executable tool availability. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a per-alias audit result indicating whether each client alias maps one-to-one to the declared contract's owner, revision, input pin, and output pin; flags any mismatches or unresolved crosswalks. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mappings": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "contracts": {
   "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/api-contracts-identifier-crosswalk-audit-1e72d5e5/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)