# Change Audit: Cargo Make

> Change Audit: Cargo Make 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 audits JSON changes between a before/after pair for Cargo Make configuration files, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-cargo-make-16220c88-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-cargo-make-e1a4053b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bm0ARAPHGTAqGVHt5whTJ

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-cargo-make-e1a4053b -d '<json body>'
```

Example prompt: Can you audit my Cargo Make config changes — here's the before JSON and the after JSON — and tell me which fields were added or removed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you need schema-aware change auditing specifically for Cargo Make JSON configuration files, want to pinpoint exactly which JSON pointer paths changed and whether those changes introduced or resolved SchemaStore violations, and need a low-cost ($0.01 USDC) per-audit call. It is not suitable for YAML/TOML formats, non-Cargo-Make schemas, or documents larger than 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Input is YAML or TOML rather than JSON — not supported
- Malformed JSON in before or after field — parse error
- Network or payment processing failure — no result returned

## How this service works

Change audit: Cargo Make: Audit JSON changes and validate before/after for Cargo Make. 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 pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, based on a pinned SchemaStore definition for Cargo Make. Covers documents up to 100 KB and 32 nesting levels.

## 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-cargo-make-e1a4053b/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)