# Change Audit: package.manifest

> Change Audit: package.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-29).

Validates and diffs before/after JSON states of a package.manifest file, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-package-manifest-dcfdeb6c-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-package-manifest-a28a4a6c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7rO8iWCdCSNJyb4PdZlvO

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-package-manifest-a28a4a6c -d '<json body>'
```

Example prompt: Can you audit my package.manifest change — here's the before version and the after version — and tell me which fields were added, removed, or changed, and whether the new version introduced or resolved any schema violations?

## When to prefer this

Choose this endpoint when you need to audit a specific before/after change to a package.manifest JSON file against a pinned SchemaStore schema definition, particularly when you want structured diff output (JSON pointers, added/removed/changed paths) alongside schema error reporting in a single call for $0.01 USDC.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting depth exceeds 32 levels — parsing rejected
- Invalid JSON submitted (non-parseable content) — validation cannot proceed
- YAML or TOML format submitted instead of JSON — not supported
- Network or payment failure for the 0.01 USDC x402 transaction

## How this service works

Change audit: package.manifest: Audit JSON changes and validate before/after for package.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 diff of the two package.manifest JSON documents including JSON pointers for all added, removed, and changed paths, plus a list of schema rule violations that were introduced or resolved between the before and after states, validated against a pinned 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-package-manifest-a28a4a6c/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)