# Prisma.yml Change Audit

> Prisma.yml 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-20).

Audits JSON changes between before/after versions of prisma.yml, reporting added/removed/changed paths, JSON pointer violations, and introduced/resolved schema errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-prisma-yml-9d34fd4f-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prisma-yml-change-audit-56294fe5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8sD8l29D72S-xAtsIekVD

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 prisma-yml-change-audit-56294fe5 -d '<json body>'
```

Example prompt: Compare these two prisma.yml configs and tell me what JSON paths changed, what new schema violations were introduced, and what errors were resolved — here's the before value and the after value.

## When to prefer this

Choose this endpoint when you need a diff-aware schema validation of prisma.yml specifically — it uses a pinned SchemaStore definition and reports both structural changes (added/removed/changed paths) and semantic changes (introduced/resolved rule violations) in a single call. Prefer it over generic JSON diff tools when you need schema-rule awareness, or over full deployment validators when you only need configuration-level change auditing without deployment or security guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Non-JSON input (YAML/TOML) submitted — not parsed, error returned
- Malformed JSON in before or after field — validation cannot proceed
- SchemaStore definition unavailable or pinned version mismatch — may produce incomplete results

## How this service works

Change audit: prisma.yml: Audit JSON changes and validate before/after for prisma.yml. 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 of JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations introduced or resolved, and any SchemaStore-based validation errors for the prisma.yml format. Up to 100 KB per document.

## 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/prisma-yml-change-audit-56294fe5/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)