# Gematik Health Care Provider List Change Audit

> Gematik Health Care Provider List 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-18).

Validates and diffs two JSON documents (before/after) against a pinned gematik health care provider list schema, reporting added/removed/changed paths and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-gematik-health-care-provid-8c3dd093-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gematik-health-care-provider-list-change-audit-bc72cf5b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MOdRnCIS5A3OY2nnLqc50

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 gematik-health-care-provider-list-change-audit-bc72cf5b -d '<json body>'
```

Example prompt: I updated the gematik health care provider list JSON — can you audit the changes by comparing the old version and the new version, and tell me which paths were added, removed, or changed, and whether any new schema violations were introduced or old ones were resolved?

## When to prefer this

Use this endpoint when you specifically need to audit changes to a gematik health care provider list JSON against a pinned SchemaStore schema definition, and want both a structural diff (added/removed/changed paths) and a schema validation delta (introduced vs. resolved errors) in a single call. Prefer it over generic JSON diff tools when gematik schema compliance is required, and over generic validators when you need to track what changed between two versions simultaneously.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing halted
- Invalid JSON submitted for before or after — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Schema definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: gematik health care provider list: Audit JSON changes and validate before/after for gematik health care provider list. 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

A structured report listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations that were introduced or resolved, based on the pinned gematik health care provider list SchemaStore definition. Documents must be under 100 KB and 32 nesting levels.

## 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/gematik-health-care-provider-list-change-audit-bc72cf5b/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)