# Change Audit: AlgoVoi Compliance Receipt v1

> Change Audit: AlgoVoi Compliance Receipt v1 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-16).

Audits JSON changes between two documents (before/after) against the AlgoVoi Compliance Receipt v1 schema, reporting added/removed/changed paths, JSON pointer violations, and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-algovoi-compliance-receipt-458f2fb8-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-algovoi-compliance-receipt-v1-428dfec2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M9L7KLDHSIAfwjilrQ2WY

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-algovoi-compliance-receipt-v1-428dfec2 -d '<json body>'
```

Example prompt: Can you audit the changes I made to this AlgoVoi Compliance Receipt — here's the before and after JSON — and tell me which fields changed, which schema rules are now violated, and whether any existing errors got resolved?

## When to prefer this

Use this endpoint when you specifically need to audit changes to AlgoVoi Compliance Receipt v1 JSON documents and want both a structural diff (added/removed/changed paths) and schema validation (rule violations, introduced/resolved errors) in a single call. Prefer this over generic JSON diff tools when compliance schema enforcement against the pinned AlgoVoi Compliance Receipt v1 definition is required.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Invalid JSON submitted in before or after field — parse error returned
- YAML or TOML input submitted instead of JSON — not supported
- Schema unavailable or pinned definition mismatch — validation may be incomplete

## How this service works

Change audit: AlgoVoi Compliance Receipt v1: Audit JSON changes and validate before/after for AlgoVoi Compliance Receipt v1. 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 all JSON pointer paths that were added, removed, or modified between the before and after documents, along with any schema rule violations, newly introduced errors, and errors that were resolved by the change — evaluated against the pinned AlgoVoi Compliance Receipt v1 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-algovoi-compliance-receipt-v1-428dfec2/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)