# Change Audit: gematik Health Care Provider Institution List

> Change Audit: gematik Health Care Provider Institution List 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-16).

Audits JSON changes (before/after) for the gematik health care provider institution list schema, validating both documents and reporting added/removed/changed paths and errors.

## Facts

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

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

Example prompt: Can you audit the changes between my old and new gematik health care provider institution list JSON files — show me what paths were added, removed, or changed, and flag any schema violations that were introduced or resolved?

## When to prefer this

Choose this endpoint when you specifically need to validate JSON documents against the gematik health care provider institution list schema and want a diff-style audit showing what changed between two versions. It is ideal for healthcare IT workflows involving gematik-compliant data pipelines where schema compliance must be tracked across updates. Not suitable for YAML/TOML, documents over 100 KB, or non-gematik schemas.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON depth exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — validation cannot proceed
- Schema unavailable or SchemaStore definition mismatch — results may be incomplete
- YAML or TOML input submitted instead of JSON — not supported

## How this service works

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

Returns a structured report listing JSON pointers and rule violations, paths that were added, removed, or changed between the before and after documents, plus errors that were introduced or resolved — all validated against the pinned gematik health care provider institution list 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/change-audit-gematik-health-care-provider-institution-list-105beee0/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)