# MapEHR Mapping JSON Change Audit

> MapEHR Mapping JSON Change Audit is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-19).

Audits JSON changes between two MapEHR Mapping documents, reporting added/removed/changed paths and introduced/resolved schema violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-mapehr-mapping-d3674280-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mapehr-mapping-json-change-audit-612a1bb2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BoV98fumMVVbZx14orapq

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 mapehr-mapping-json-change-audit-612a1bb2 -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new MapEHR Mapping JSON configs — tell me what paths were added, removed, or changed, and flag any schema violations that were introduced or resolved?

## When to prefer this

Use this endpoint when you specifically need to audit changes to MapEHR Mapping JSON documents against the pinned SchemaStore schema — it is purpose-built for the MapEHR Mapping format and reports both structural diffs (added/removed/changed paths) and schema compliance changes (introduced/resolved violations) in a single call. Prefer it over generic JSON diff tools when schema rule enforcement against the MapEHR Mapping definition matters.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Malformed JSON in before or after fields — validation cannot proceed
- Payment not included or insufficient — endpoint returns 402
- SchemaStore definition unavailable for MapEHR Mapping — validation skipped

## How this service works

Change audit: MapEHR Mapping: Audit JSON changes and validate before/after for MapEHR Mapping. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations, added/removed/changed paths and introduced/resolved errors. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one two-document change audit.

## Output

Returns a structured audit report containing JSON pointers to all added, removed, and changed paths between the before and after documents, along with any schema rule violations that were introduced or resolved, validated against a pinned MapEHR Mapping SchemaStore definition.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "default": {
    "agent_market_example": true
   },
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  },
  "before": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mapehr-mapping-json-change-audit-612a1bb2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)