# Change Audit: project.json

> Change Audit: project.json 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-23).

Audits before/after JSON changes for project.json files, validating against a pinned SchemaStore definition and reporting added/removed/changed paths plus introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-project-json-8384cfb8-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-project-json-53775934
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NDFGcEoBbY7StwLPfY--l

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-project-json-53775934 -d '<json body>'
```

Example prompt: Can you audit my project.json changes? Here's the before version and the after version — tell me what paths were added, removed, or changed, and whether any new schema errors were introduced or old ones resolved.

## When to prefer this

Choose this endpoint when you need to audit exactly what changed between two project.json documents and whether those changes comply with the SchemaStore-defined schema, especially in CI/CD pipelines, code review automation, or debugging broken project configurations. It is specifically scoped to project.json and uses a pinned schema definition, making it more precise than a generic JSON diff or generic JSON Schema validator.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing fails
- Invalid JSON submitted (not parseable) — error returned
- YAML or TOML input submitted instead of JSON — not supported
- Payment not provided or insufficient — request blocked

## How this service works

Change audit: project.json: Audit JSON changes and validate before/after for project.json. 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 differences between the before and after documents, including added, removed, and changed paths, along with introduced and resolved schema rule violations based on a pinned SchemaStore definition for project.json. Limited to documents up to 100 KB and 32 nesting levels each.

## 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-project-json-53775934/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)