# Change Audit: dotnet Release Index Manifest

> Change Audit: dotnet Release Index Manifest 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).

Audits JSON changes between two dotnet Release Index manifest documents, validating both against a pinned SchemaStore schema and reporting added/removed/changed JSON paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-dotnet-release-index-manif-b509c524-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-dotnet-release-index-manifest-b78b98fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_47qpv0THaKkl2GO7uedOE

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-dotnet-release-index-manifest-b78b98fd -d '<json body>'
```

Example prompt: Can you audit the change I made to my dotnet Release Index manifest — here's the before and after JSON — and tell me what paths were added, removed, or changed, and whether any new schema violations were introduced?

## When to prefer this

Use this endpoint when you need to audit a specific change to a dotnet Release Index manifest JSON file — especially when you want both a structural diff (what paths changed) and schema validation feedback (what errors were introduced or resolved) in a single call. Prefer this over generic JSON diff tools when dotnet Release Index manifest schema compliance is required and you want SchemaStore-backed validation.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON submitted (non-parseable input) — validation cannot proceed
- YAML or TOML format submitted instead of JSON — not supported
- Schema mismatch due to SchemaStore pinning — may not reflect latest upstream schema changes

## How this service works

Change audit: dotnet Release Index manifest: Audit JSON changes and validate before/after for dotnet Release Index manifest. 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 two documents, along with schema validation results for both the before and after documents, including which errors were introduced or resolved by the change. Up to 100 KB per document is supported.

## 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-dotnet-release-index-manifest-b78b98fd/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)