# Change Audit: nuget-project.json

> Change Audit: nuget-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-24).

Validates and diffs two versions of a nuget-project.json document, reporting added/removed/changed JSON paths and introduced/resolved schema violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-nuget-project-json-60578f3b-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-nuget-project-json-d65b8122
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-rGRsY4TM3-wdWKOOY8iU

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

Example prompt: Can you audit the changes I made to my nuget-project.json — here's the before version and the after version — and tell me what paths changed and whether I introduced or fixed any schema errors?

## When to prefer this

Use this endpoint when you need a precise, schema-aware diff of two nuget-project.json documents that shows not only structural changes (added/removed/changed paths) but also whether those changes introduced or resolved schema violations per SchemaStore rules. Prefer this over generic JSON diff tools when NuGet-specific schema validation is required.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML input mistakenly submitted — not supported
- Missing before or after field — incomplete audit result

## How this service works

Change audit: nuget-project.json: Audit JSON changes and validate before/after for nuget-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 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 a pinned SchemaStore definition for nuget-project.json.

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